CVE-2026-77805: Weak Executable Signature Verification Vulnerability in Progress® Telerik® Fiddler® Classic
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Progress Telerik Fiddler Classic for Windowsto a version that resolves this vulnerability.Fixed in 6.0.20262.10021
Event History
Frequently Asked Questions
Does an attacker need administrative privileges to exploit this issue?
No. A local attacker with low privileges can replace an external helper executable, but exploitation depends on the affected application later launching that tool and the user approving its elevation prompt.
Can an attacker substitute any executable for a helper tool?
No. The substituted file must carry a valid Authenticode signature with a certificate subject name matching the application's broad allow list of publisher-name fragments. The validation does not confirm that it is the specific helper executable shipped with that product version.
What user interaction is required for privilege escalation?
The user must launch the affected external tool and approve the elevation prompt, without noticing that the prompt refers to a different executable.