CVE-2026-77802: Progress® Telerik® Fiddler® Classic · HTTP Request/Response Smuggling
Affects Progress® Telerik® Fiddler® ClassicSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 6.0.20262.10021 when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% 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:H/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Progress SoftwareProgress® Telerik® Fiddler® Classic | Affected
| Fixed in
|
AI-suggested
A fix is available in Progress® Telerik® Fiddler® Classic version 6.0.20262.10021 and later. Users should upgrade to this version or newer to remediate the vulnerability. No other mitigation guidance is provided in the vendor advisory.
Description
CVE-2026-77802 is a medium severity vulnerability in Progress® Telerik® Fiddler® Classic for Windows prior to version 6.0.20262.10021. It involves HTTP request smuggling due to inconsistent handling of multiple conflicting Content-Length headers in the proxy request forwarding component. A local attacker with low privileges can exploit this to smuggle additional requests against non-RFC-9110-compliant origin servers that keep connections alive. This can lead to response poisoning and unauthorized access to responses intended for other users.