{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77805 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77805 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77805 is a high-severity vulnerability in Progress® Telerik® Fiddler® Classic, published on 5 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-77805 and fix it if it is affected.\n\nWhat it is: CVE-2026-77805 is a high-severity vulnerability in Progress® Telerik® Fiddler® Classic, published on 5 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-77805 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-77805/ (Markdown: https://insights.sbomify.com/CVE-2026-77805/index.md)","id":"CVE-2026-77805","markdown":"https://insights.sbomify.com/CVE-2026-77805/index.md","name":"CVE-2026-77805","record":{"aliases":["GHSA-mpj7-wp32-q53h"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Fiddler Classic","requires_auth":"low_privilege","summary":"Local attackers can bypass signature checks to execute arbitrary signed binaries with elevated privileges, requiring user interaction to approve elevation prompts.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ProgressSoftware","cpe":[],"cvss":{"score":7.9,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"In Progress® Telerik® Fiddler® Classic for Windows, versions prior to v6.0.20262.10021, the integrity check applied to the external helper tools launched by the application is insufficient. Before executing a helper tool, the application only verifies that the file carries a valid Authenticode signature whose certificate subject name matches a broad allow list of publisher name fragments, rather than verifying that the file is the specific executable shipped with that version of the product. A local threat actor with low privileges who replaces one of these helper executables with any other validly signed binary from an allow-listed publisher can cause the substituted binary to be executed by the application, including with Administrator privileges for the tools that request elevation, resulting in privilege escalation and execution of unintended code. Successful exploitation requires the user to launch the affected external tool and to approve the elevation prompt without noticing that it refers to a different executable.","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":"Weak Executable Signature Verification Vulnerability in Progress® Telerik® Fiddler® Classic","id":"CVE-2026-77805","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in SPIP","id":"CVE-2026-77806"},"packages":[],"prev":{"headline":"Race condition in Progress® Telerik® Fiddler® Classic","id":"CVE-2026-77804"},"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-05","vendors":["Progress Software"]},"summary":"Local attackers can bypass signature checks to execute arbitrary signed binaries with elevated privileges, requiring user interaction to approve elevation prompts.","url":"https://insights.sbomify.com/CVE-2026-77805/"}