LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27633: TinyWeb has Unbounded Content-Length Memory Exhaustion (DoS)

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).

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27633 is a denial-of-service flaw in TinyWeb before 2.02. A remote unauthenticated user can make the server consume memory until it crashes. This affects organizations hosting services with TinyWeb. The vendor-provided fix is version 2.02, which adds a maximum request body size.

Executive priority

Treat as high priority for internet-facing TinyWeb services because it can cause outage without authentication. Prioritize confirming use of TinyWeb, upgrading to 2.02, or enforcing request body limits through a front-end control until upgrade is complete.

Technical view

TinyWeb before 2.02 does not enforce a maximum EntityBody size when processing HTTP POST requests with very large Content-Length values. The server keeps allocating memory while receiving the body, causing memory exhaustion and crash. The issue is classified as CWE-400 and has CVSS 4.0 score 8.7, with network attack vector and no privileges required.

Likely exposure

Exposure is limited to systems running TinyWeb versions earlier than 2.02, especially internet-facing HTTP or HTTPS services. Anyone hosting services using TinyWeb is described as impacted. Environments not using TinyWeb are not affected based on the provided sources.

Exploitation context

The sources describe unauthenticated remote denial of service through oversized HTTP request bodies. CISA KEV status is false in the provided bundle, and no cited source states active exploitation. The practical impact is service outage from process crash or host memory pressure.

Researcher notes

The public advisory and CVE record identify the root cause as unbounded request body allocation. The referenced commit introduces CMaxEntityBodySize set to 10MB. Do not assume broader product impact beyond TinyWeb before 2.02 based on the available sources.

Mitigation direction

  • Upgrade TinyWeb to version 2.02 or later.
  • If upgrade is delayed, place TinyWeb behind a WAF or reverse proxy.
  • Configure explicit maximum HTTP request body size limits at the proxy.
  • Monitor vendor advisory and project repository for additional guidance.

Validation and detection

  • Inventory systems running TinyWeb and record versions.
  • Confirm any TinyWeb instance below 2.02 is prioritized for remediation.
  • Check reverse proxy or WAF request body size limits.
  • Review service monitoring for unexplained TinyWeb crashes or memory exhaustion.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27633 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-27633Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
maximmasiutinTinyWeb< 2.02Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.