{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-61642 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-61642 is a high-severity vulnerability in squid-cache squid, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-61642 and fix it if it is affected.\n\nWhat it is: CVE-2026-61642 is a high-severity vulnerability in squid-cache squid, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-61642 in the wild and no public exploit code.\n\nAffected product: squid-cache squid. 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-61642/ (Markdown: https://insights.sbomify.com/CVE-2026-61642/index.md)","id":"CVE-2026-61642","markdown":"https://insights.sbomify.com/CVE-2026-61642/index.md","name":"CVE-2026-61642","record":{"aliases":["AZL-108531","CLSA-2026-1792505835","CLSA-2026-1792517219","CLSA-2026-1792806435","DEBIAN-CVE-2026-61642","GHSA-537g-4gfh-w7m6","OESA-2026-4580","OESA-2026-4581","OESA-2026-4582","OESA-2026-4583","UBUNTU-CVE-2026-61642"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Web caching proxy","requires_auth":"low_privilege","summary":"Attackers can smuggle HTTP requests to bypass security controls and poison web caches, affecting Squid proxy deployments.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"Squid is a caching proxy for the Web. From 3.3.0.1 to before 7.6, due to an improper enforcement of behavioral workflow bug, Squid is vulnerable to a Request Smuggling attack against HTTP/1.1 Transfer-Encoding. HTTP header parsing (`src/HttpHeader.cc`) accepted the bare` Transfer-Encoding:` identity form, which the HTTP specification prohibits because any transfer coding must be wrapped within chunked encoding. This problem allows a trusted client to perform an HTTP Request Smuggling attack when HTTP/1.1 is used, bypassing security mechanisms that may be in place between attacker and Squid. When there is an HTTP cache operating prior to the affected Squid, this Request Smuggling attack also allows the attacker to poison that web cache and store arbitrary malicious content at any URL for delivery to other clients' future requests. This issue is fixed in version 7.6.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Squid Request Smuggling in HTTP Transfer-Encoding","id":"CVE-2026-61642","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"FastGPT: workflow runtime can execute another user's private HTTP toolset","id":"CVE-2026-61643"},"packages":[],"prev":{"headline":"Wallos: OIDC account takeover via email-based account linking without `email_verified` check","id":"CVE-2026-61641"},"products":["squid"],"published":"2026-10-13","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-13","vendors":["squid-cache"]},"summary":"Attackers can smuggle HTTP requests to bypass security controls and poison web caches, affecting Squid proxy deployments.","url":"https://insights.sbomify.com/CVE-2026-61642/"}