CVE-2026-27630
Published: 26 February 2026
Summary
CVE-2026-27630 is a high-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Ritlabs Tinyweb. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Service Exhaustion Flood (T1499.002); ranked at the 33.9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Threat & Defense at a Glance
Threat & Defense Details
Likely Mitigating ControlsAI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Limiting concurrent sessions directly prevents uncontrolled resource consumption by capping the number of active sessions per user or account.
Contingency plan testing includes resource exhaustion scenarios to verify recovery, making it harder for attackers to sustain exploits that cause uncontrolled consumption.
Updated contingency plans include current procedures to detect, contain, and recover from resource exhaustion, limiting an attacker's ability to sustain impact from uncontrolled consumption.
Alternate site allows resumption of operations if resource exhaustion at the primary site is exploited to cause unavailability.
Alternate telecommunications services enable resumption of essential functions when primary services become unavailable due to uncontrolled resource consumption.
Planning and coordination of security activities (scans, tests, maintenance) directly imposes scheduling and throttling that prevents those activities from producing uncontrolled resource consumption.
Performance metrics and monitoring inherently track resource consumption patterns, making uncontrolled consumption easier to detect and mitigate.
Terminating idle connections bounds resource consumption that would otherwise allow uncontrolled accumulation of open sessions.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The vulnerability directly enables a Slowloris-style resource exhaustion attack against the web server by allowing an attacker to tie up threads via slow partial requests, mapping to service exhaustion for endpoint DoS.
NVD Description
TinyWeb is a web server (HTTP, HTTPS) written in Delphi for Win32. Versions prior to version 2.02 are vulnerable to a Denial of Service (DoS) attack known as Slowloris. The server spawns a new OS thread for every incoming connection…
more
without enforcing a maximum concurrency limit or an appropriate request timeout. An unauthenticated remote attacker can exhaust server concurrency limits and memory by opening numerous connections and sending data exceptionally slowly (e.g. 1 byte every few minutes). Anyone hosting services using TinyWeb is impacted. Version 2.02 fixes the issue. The patch introduces a `CMaxConnections` limit (set to 512) and a `CConnectionTimeoutSecs` idle timeout (set to 30 seconds). As a temporary workaround if upgrading is not immediately possible, consider placing the server behind a robust reverse proxy or Web Application Firewall (WAF) such as nginx, HAProxy, or Cloudflare, configured to buffer incomplete requests and aggressively enforce connection limits and timeouts.
Deeper analysisAI
CVE-2026-27630 is a Denial of Service vulnerability affecting TinyWeb, a lightweight web server for HTTP and HTTPS written in Delphi for Win32 platforms. Versions prior to 2.02 are susceptible to a Slowloris-style attack due to the server spawning a new operating system thread for every incoming connection without enforcing a maximum concurrency limit or an appropriate request timeout. This flaw, associated with CWE-400 (Uncontrolled Resource Consumption) and CWE-770 (Allocation of Resources Without Limits or Throttling), carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
An unauthenticated remote attacker can exploit the vulnerability by establishing numerous connections to the server and transmitting data at an exceptionally slow rate, such as 1 byte every few minutes. This partial request technique ties up server threads and exhausts available memory and concurrency limits, rendering the server unresponsive to legitimate traffic and causing a denial of service.
Version 2.02 addresses the issue by introducing a CMaxConnections limit defaulting to 512 and a CConnectionTimeoutSecs idle timeout of 30 seconds. Advisories recommend upgrading to this patched version, with commit details available at the project's GitHub repository. As a temporary mitigation if immediate upgrading is not feasible, deploy the server behind a robust reverse proxy or Web Application Firewall such as nginx, HAProxy, or Cloudflare, configured to buffer incomplete requests and strictly enforce connection limits and timeouts. Further guidance is provided in the GitHub security advisory and related blog post.
Details
- CWE(s)