LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27630: TinyWeb vulnerable to Remote Denial of Service via Thread/Connection Exhaustion (Slowloris)

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.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-27630 can let an unauthenticated remote attacker make TinyWeb unavailable by tying up server threads and memory with many slow connections. It affects TinyWeb versions before 2.02. The issue is availability-only, but it can disrupt any service hosted on vulnerable TinyWeb deployments.

Executive priority

Prioritize remediation for internet-facing TinyWeb services because exploitation requires no credentials and can cause service outage. Internal-only deployments are lower urgency but should still be upgraded during normal maintenance.

Technical view

TinyWeb before 2.02 creates a new OS thread per incoming connection without a maximum concurrency limit or suitable request timeout. This enables Slowloris-style resource exhaustion over the network without authentication or user interaction. Version 2.02 adds a 512-connection cap and a 30-second idle connection timeout.

Likely exposure

Organizations are exposed if they host HTTP or HTTPS services using TinyWeb versions earlier than 2.02, especially if the service is reachable from untrusted networks or the internet.

Exploitation context

Sources describe a remote, unauthenticated denial-of-service condition using slow connection behavior. The CVE is not listed as KEV, and the provided sources do not state active exploitation in the wild.

Researcher notes

The public record identifies CWE-400 resource exhaustion and CVSS 4.0 score 8.7. Evidence supports an availability impact only; confidentiality and integrity impacts are not indicated. The fix is documented as commit 23268c8 and TinyWeb 2.02.

Mitigation direction

  • Upgrade TinyWeb to version 2.02 or later.
  • If upgrade is delayed, place TinyWeb behind a robust reverse proxy or WAF.
  • Configure proxy connection limits, request buffering, and aggressive idle timeouts.
  • Limit direct internet exposure to TinyWeb where possible.
  • Monitor for abnormal connection counts, thread growth, and memory pressure.

Validation and detection

  • Inventory systems running TinyWeb and identify exposed HTTP or HTTPS services.
  • Confirm TinyWeb version is 2.02 or later.
  • Review whether the 2.02 connection cap and idle timeout are present.
  • Verify reverse proxy or WAF timeout and connection-limit settings.
  • Check logs and telemetry for availability incidents tied to connection 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-27630 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-27630Attack 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.