{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77802 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77802 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77802 is a medium-severity vulnerability in Progress® Telerik® Fiddler® Classic, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77802 and fix it if it is affected.\n\nWhat it is: CVE-2026-77802 is a medium-severity vulnerability in Progress® Telerik® Fiddler® Classic, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-77802 in the wild and no public exploit code.\n\nAffected product: Progress® Telerik® Fiddler® Classic. 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-77802/ (Markdown: https://insights.sbomify.com/CVE-2026-77802/index.md)","id":"CVE-2026-77802","markdown":"https://insights.sbomify.com/CVE-2026-77802/index.md","name":"CVE-2026-77802","record":{"aliases":["GHSA-p3gc-87rm-gmjp"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"HTTP debugging proxy","requires_auth":"low_privilege","summary":"A local attacker can exploit HTTP request smuggling in Fiddler Classic to poison responses and read data intended for other users sharing the proxy.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ProgressSoftware","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"In Progress® Telerik® Fiddler® Classic for Windows, versions prior to v6.0.20262.10021, HTTP request smuggling is possible in the proxy request forwarding component. Requests containing multiple Content-Length headers with conflicting values are forwarded verbatim to the origin server, while Fiddler frames the request body using only the first Content-Length value. A local threat actor with low privileges who is able to send requests through the same Fiddler proxy instance as another user can exploit this desynchronization against a non-RFC-9110-compliant origin server that keeps the connection alive to smuggle an additional request. Because Fiddler returns the server connection to its pipe pool after reading only the first response, the unread smuggled response remains buffered on the socket and is served to the next session that reuses that connection, allowing the attacker to poison responses delivered to other users and to obtain responses intended for them.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"HTTP Request Smuggling Vulnerability in Progress® Telerik® Fiddler® Classic","id":"CVE-2026-77802","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Front-end Desynchronization Vulnerability in Progress® Telerik® Fiddler® Classic","id":"CVE-2026-77803"},"packages":[],"prev":{"headline":"Allocation of Resources Without Limits or Throttling in GitLab","id":"CVE-2026-77801"},"products":["Progress® Telerik® Fiddler® Classic"],"published":"2026-10-05","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":"total"},"state":"PUBLISHED","updated":"2026-10-06","vendors":["Progress Software"]},"summary":"A local attacker can exploit HTTP request smuggling in Fiddler Classic to poison responses and read data intended for other users sharing the proxy.","url":"https://insights.sbomify.com/CVE-2026-77802/"}