Skip to content
Web

CVE-2026-67184

8.7
High
EPSS 0.43%Jul 29, 2026

Malformed HTTP version parsing in TinyWeb allows unauthenticated requests to crash worker processes.

common questions

Is CVE-2026-67184 being exploited?

Not confirmed. CVE-2026-67184 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.43% probability of exploitation in the next 30 days.

How severe is CVE-2026-67184?

CVE-2026-67184 is rated High with a CVSS score of 8.7. 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-67184?

Not known from our data. No patch reference has been recorded for CVE-2026-67184, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-67184 affect?

CVE-2026-67184 affects TinyWeb <= 0.0.8, Servers running TinyWeb. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-67184?

Block malformed request lines via WAF/nginx, rate-limit, restart affected workers; update TinyWeb when patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TinyWeb <= 0.0.8Servers running TinyWeb
impact

Unauthenticated remote attackers can trigger a NULL dereference via malformed HTTP version, causing SIGSEGV and complete server DoS.

action required

Immediate action required

affected versions
GeneralSandman TinyWeb
  • affected>= e48f15d38d2bebeec9cabcfdde81931b10a1963b and <= a381da252fe8e873c8aff22703040426cc9b2ae0
  • affected0.0.8

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free