CVE-2026-28497
HTTP request smuggling via integer overflow in TinyWeb <=2.02.
Is CVE-2026-28497 being exploited?
Not confirmed. CVE-2026-28497 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-28497?
CVE-2026-28497 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-28497?
Yes. A fix has been recorded for CVE-2026-28497. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-28497 affect?
CVE-2026-28497 affects TinyWeb web server (Win32) <= 2.02. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-28497?
Upgrade to TinyWeb 2.03+ to fix the issue.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote smuggling allows bypass of Content-Length, enabling unauthorized access, filter bypass, and cache poisoning under Keep-Alive.
Patch when possible
- affected< 2.03
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.