{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67183 exists.","fix":"No fix has been published for CVE-2026-67183 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67183 is a high-severity denial of service vulnerability in GeneralSandman TinyWeb, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-67183 and fix it if it is affected.\n\nWhat it is: CVE-2026-67183 is a high-severity denial of service vulnerability in GeneralSandman TinyWeb, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67183 exists.\n\nAffected product: GeneralSandman TinyWeb. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-67183/ (Markdown: https://insights.sbomify.com/CVE-2026-67183/index.md)","id":"CVE-2026-67183","markdown":"https://insights.sbomify.com/CVE-2026-67183/index.md","name":"CVE-2026-67183","record":{"aliases":["GHSA-9hxr-3mx5-3v44"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"TinyWeb web server","requires_auth":"none","summary":"Unauthenticated attackers can exhaust memory and crash the TinyWeb server by sending standard HTTP requests due to improper resource management.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-07-26","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-26T15:08:19Z","kind":"github_poc","ref":"https://github.com/theopaid/CVE-2026-67183-Unauthenticated-Memory-Leak-Leads-To-Memory-Exhaustion-TinyWeb-","stars":0,"title":"Security Advisory: Unauthenticated Memory Leak Leads To Memory Exhaustion (TinyWeb)"}],"tier":"weaponised"},"has_fix":false,"headline":"TinyWeb 0.0.8 Memory Leak DoS via HTTP Request Handling","id":"CVE-2026-67183","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"TinyWeb 0.0.8 Null Pointer Dereference DoS via Malformed HTTP Request","id":"CVE-2026-67184"},"packages":[],"prev":{"headline":"Rouille 0.3.3 - 3.6.2 HTTP Request Smuggling via proxy Header Injection","id":"CVE-2026-67182"},"products":["TinyWeb"],"published":"2026-07-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["GeneralSandman"]},"summary":"Unauthenticated attackers can exhaust memory and crash the TinyWeb server by sending standard HTTP requests due to improper resource management.","url":"https://insights.sbomify.com/CVE-2026-67183/"}