Skip to main content
VulnerabilityPublished

CVE-2026-77805: Progress® Telerik® Fiddler® Classic · Improper Verification of Cryptographic Signature

Affects Progress® Telerik® Fiddler® ClassicSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.9 High : upgrade to 6.0.20262.10021 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
7.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.06% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.0.20262.10021
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade Progress® Telerik® Fiddler® Classic to 6.0.20262.10021.

Affected software

ProductAffectedFixed in
Progress SoftwareProgress® Telerik® Fiddler® ClassicAffected
  • >=1.0.0 <6.0.20262.10021
Fixed in
  • 6.0.20262.10021

AI-suggested

If you cannot patch yet, users should exercise caution when launching external helper tools and carefully verify elevation prompts. Restrict local user permissions to prevent unauthorized replacement of helper executables.

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.

References

Community reviews

Loading reviews…