CVE-2026-27630: maximmasiutin TinyWeb · Uncontrolled Resource Consumption
Affects maximmasiutin TinyWebSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 2.02 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.02
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade TinyWeb and maximmasiutin/TinyWeb to 2.02.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| maximmasiutinTinyWeb | Affected
| Fixed in
|
GitHubmaximmasiutin/TinyWebpkg:github/maximmasiutin/TinyWebOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade TinyWeb to version 2.02 or later immediately to apply the built-in fix introducing connection limits and timeouts.
- If immediate upgrade is not feasible, deploy TinyWeb behind a robust reverse proxy or Web Application Firewall (WAF) such as nginx, HAProxy, or Cloudflare. Configure these intermediaries to buffer incomplete HTTP requests, enforce strict maximum connection limits, and apply aggressive idle connection timeouts (e.g., 30 seconds or less).
- Monitor server metrics closely for unusual connection patterns or resource usage spikes indicative of Slowloris-style attacks.
- Implement network-level rate limiting and anomaly detection to identify and block suspicious slow connection attempts.
- Consider disabling or restricting access to TinyWeb services from untrusted networks or IP ranges to reduce exposure.
- Regularly audit and update all web-facing infrastructure to ensure timely application of security patches and mitigations.
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 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.