Skip to main content
VulnerabilityPublished

CVE-2026-27633: maximmasiutin TinyWeb · Uncontrolled Resource Consumption

Affects maximmasiutin TinyWebSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 2.02 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Upgrade TinyWeb and maximmasiutin/TinyWeb to 2.02.

Affected software

ProductAffectedFixed in
maximmasiutinTinyWebAffected
  • <2.02
Fixed in
  • 2.02
GitHubmaximmasiutin/TinyWebpkg:github/maximmasiutin/TinyWebOther threatsAffected
  • <2.02
Fixed in
  • 2.02

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade TinyWeb to version 2.02 or later immediately to apply the official patch that enforces a maximum request body size of 10MB.
  2. If immediate upgrade is not feasible, deploy a Web Application Firewall (WAF) or reverse proxy (e.g., nginx, Cloudflare) in front of TinyWeb servers. Configure these intermediaries to explicitly limit the maximum allowed HTTP request body size (for example, set nginx’s client_max_body_size to 10MB or less).
  3. Monitor web server logs for unusually large Content-Length headers or repeated POST requests that could indicate exploitation attempts.
  4. Implement network-level rate limiting and anomaly detection to identify and block suspicious traffic patterns targeting TinyWeb servers.
  5. Conduct regular vulnerability scanning and penetration testing to ensure no other resource exhaustion vectors exist.
  6. Educate system administrators about this vulnerability and ensure patch management processes prioritize this update.
  7. Consider isolating TinyWeb services in segmented network zones to limit potential impact of DoS attacks.

Description

TinyWeb is a web server (HTTP, HTTPS) written in Delphi for Win32. Versions prior to version 2.02 have a Denial of Service (DoS) vulnerability via memory exhaustion. Unauthenticated remote attackers can send an HTTP POST request to the server with an exceptionally large `Content-Length` header (e.g., `2147483647`). The server continuously allocates memory for the request body (`EntityBody`) while streaming the payload without enforcing any maximum limit, leading to all available memory being consumed and causing the server to crash. Anyone hosting services using TinyWeb is impacted. Version 2.02 fixes the issue. The patch introduces a `CMaxEntityBodySize` limit (set to 10MB) for the maximum size of accepted payloads. As a temporary workaround if upgrading is not immediately possible, consider placing the server behind a Web Application Firewall (WAF) or reverse proxy (like nginx or Cloudflare) configured to explicitly limit the maximum allowed HTTP request body size (e.g., `client_max_body_size` in nginx).

References

Community reviews

Loading reviews…