{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-66752 exists.","fix":"No fix has been published for CVE-2026-66752 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-66752 is a medium-severity vulnerability in tiny-http, 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-66752 and fix it if it is affected.\n\nWhat it is: CVE-2026-66752 is a medium-severity vulnerability in tiny-http, 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-66752 exists.\n\nAffected product: tiny-http. 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-66752/ (Markdown: https://insights.sbomify.com/CVE-2026-66752/index.md)","id":"CVE-2026-66752","markdown":"https://insights.sbomify.com/CVE-2026-66752/index.md","name":"CVE-2026-66752","record":{"aliases":["DEBIAN-CVE-2026-66752","GHSA-5hc2-r3jq-vc45","UBUNTU-CVE-2026-66752"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust HTTP library","requires_auth":"none","summary":"Attackers can desynchronize request framing or exhaust worker threads in tiny-http by exploiting improper Transfer-Encoding header handling.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"tiny-http through 0.12.0 contains an HTTP request smuggling vulnerability that allows remote attackers to desynchronize request framing by sending a Transfer-Encoding header with any value, including non-chunked codings, which causes the library to unconditionally apply chunk-decoding and discard Content-Length. Attackers can exploit the discrepancy between tiny_http's improper Transfer-Encoding parsing and a correctly-implemented front-end proxy to produce two distinct interpretations of a single byte stream, enabling request smuggling, and can additionally send non-chunked bodies with non-chunked Transfer-Encoding values to cause failed body reads that tie up connections and consume worker threads without signaling errors to clients.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-07-26","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-26T17:30:37Z","kind":"github_poc","ref":"https://github.com/theopaid/CVE-2026-66752-HTTP-Request-Smuggling-via-Unparsed-Transfer-Encoding-Values-tiny_http-","stars":0,"title":"Security Advisory: HTTP Request Smuggling via Unparsed Transfer-Encoding Values (tiny_http)"}],"tier":"weaponised"},"has_fix":false,"headline":"tiny-http 0.12.0 HTTP Request Smuggling via Transfer-Encoding Handling","id":"CVE-2026-66752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"tiny-http 0.12.0 HTTP Response Splitting via Header Injection","id":"CVE-2026-66753"},"packages":[],"prev":{"headline":"Let's Chat 0.3.0 - 0.4.8 Improper Authorization via DELETE /rooms/:room","id":"CVE-2026-66751"},"products":["tiny-http"],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["tiny-http"]},"summary":"Attackers can desynchronize request framing or exhaust worker threads in tiny-http by exploiting improper Transfer-Encoding header handling.","url":"https://insights.sbomify.com/CVE-2026-66752/"}