Skip to main content
VulnerabilityPublished Updated

CVE-2024-34199: TinyWeb · Out-of-bounds Write

Affects TinyWebSource CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 May 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubmaximmasiutin/TinyWebpkg:github/maximmasiutin/TinyWebOther threatsAffected
  • <=1.94
Fixed in–

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

AI-suggested

  1. Immediate mitigation involves restricting the maximum size of HTTP request lines at the network perimeter using web application firewalls (WAFs) or intrusion prevention systems (IPS) to block excessively large requests.
  2. Monitor network traffic for anomalous request patterns indicative of exploitation attempts.
  3. If possible, upgrade TinyWeb to a version that addresses this vulnerability once patches become available.
  4. In the absence of official patches, consider applying custom input validation or request filtering to reject oversized request lines.
  5. Implement rate limiting to reduce the risk of denial of service from repeated exploit attempts.
  6. Conduct regular vulnerability scans and penetration tests focusing on web server components to detect similar issues.
  7. Maintain an incident response plan to quickly address any service disruptions caused by exploitation attempts.
  8. Engage with vendors or open-source communities for updates or workarounds specific to TinyWeb.

Description

TinyWeb 1.94 and below allows unauthenticated remote attackers to cause a denial of service (Buffer Overflow) when sending excessively large elements in the request line.

References

Community reviews

Loading reviews…