GeneralSandman TinyWeb
TinyWeb 0.0.8 Memory Leak DoS via HTTP Request Handling
TinyWeb through 0.0.8 contains a memory leak vulnerability that allows unauthenticated attackers to exhaust available memory by sending ordinary well-formed HTTP requests. Each request causes HttpParser::execute() to allocate Url objects, HttpHeaders objects, and HttpHeader instances via raw new expressions that are never freed due to missing destructors and unreachable delete calls, causing worker resident memory to grow monotonically by approximately 20 to 28 kB per request until the worker process is killed.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= e48f15d38d2bebeec9cabcfdde81931b10a1963b, <= a381da252fe8e873c8aff22703040426cc9b2ae0
- 0.0.8
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationPublic PoC known, its date not yet looked up; not in CISA KEV.
PoC repositories
Found on GitHub.1 PoCs · 1 informational
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| theopaid/Unauthenticated-Memory-Leak-Leads-To-Memory-Exhaustion-TinyWeb- | 26 Jul 2026 −2.1 d | 0 | PoC older repo: PoC date unknown, not used for the first PoC |
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| theopaid/CVE-2026-67183-Unauthenticated-Memory-Leak-Leads-To-Memory-Exhaustion-TinyWeb- | 26 Jul 2026 −2.1 d | 0 | Informational · write-up |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.