CVE-2026-28497: maximmasiutin TinyWeb · Integer Overflow or Wraparound
Affects maximmasiutin TinyWebSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 2.03 as a priority.
Data as of 30 Oct 2026, 06:59 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.03
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Mar 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 29 Oct 2026.
What to do
Upgrade TinyWeb and maximmasiutin/TinyWeb to 2.03.
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
Organizations should immediately upgrade TinyWeb to version 2.03 or later, where the vulnerability has been patched. Until the upgrade can be applied, administrators should consider disabling persistent HTTP connections (Keep-Alive) to reduce the risk of request smuggling exploitation. Implementing strict input validation and filtering at perimeter security devices, such as web application firewalls, can help detect and block malformed HTTP requests attempting to exploit this vulnerability. Network segmentation and limiting exposure of TinyWeb servers to untrusted networks will reduce attack surface. Monitoring HTTP traffic for anomalies related to Content-Length headers and unusual request patterns can provide early detection of exploitation attempts. Additionally, conducting regular security assessments and penetration testing focused on HTTP request smuggling can help identify residual risks. Finally, organizations should maintain an inventory of all web servers in use to ensure no vulnerable TinyWeb instances remain in production.
Description
TinyWeb is a web server (HTTP, HTTPS) written in Delphi for Win32. Prior to version 2.03, an integer overflow vulnerability in the string-to-integer conversion routine (_Val) allows an unauthenticated remote attacker to bypass Content-Length restrictions and perform HTTP Request Smuggling. This can lead to unauthorized access, security filter bypass, and potential cache poisoning. The impact is critical for servers using persistent connections (Keep-Alive). This issue has been patched in version 2.03.