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.
Published: 2026-10-05
Score: 6.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Data Exposure via HTTP Request Smuggling
Action: Apply Workaround
AI Analysis

Impact

HTTP request smuggling is possible in Progress Telerik Fiddler Classic prior to v6.0.20262.10021. The proxy forwards requests containing multiple conflicting Content‑Length headers. Fiddler frames the request body using only the first header value, while the entire request is sent to the origin server. A low‑privileged local user can send a specially crafted request that smuggles an additional request to a non‑RFC‑9110‑compliant server, causing the server to keep the connection alive, thereby allowing the attacker to read or inject responses destined for other users.

Affected Systems

Affected product: Progress Telerik Fiddler Classic for Windows. All releases before v6.0.20262.10021 are vulnerable.

Risk and Exploitability

CVSS 6.3 indicates moderate severity. EPSS score is not reported, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a local low‑privileged user who can send traffic through the same proxy instance, enabling smuggling against a non‑RFC‑9110‑compliant origin server that keeps connections alive. The risk is that an attacker could poison responses delivered to other users, exposing confidential information or manipulating traffic.

Generated by OpenCVE AI on October 5, 2026 at 15:08 UTC.

Remediation

Vendor Workaround

Disable server connection reuse in Fiddler Classic: open Tools > Options > Connections and uncheck the "Reuse server connections" checkbox. Disabling server pipe reuse prevents a poisoned server connection from being handed to another session.


OpenCVE Recommended Actions

  • Disable server connection reuse in Fiddler Classic: open Tools → Options → Connections and uncheck the “Reuse server connections” checkbox.
  • Restrict local access to the Fiddler proxy so that only trusted users can send traffic through it.
  • If a vendor update that addresses the issue is available, upgrade to a version equal to or newer than v6.0.20262.10021; if none exists, monitor for forthcoming patches.

Generated by OpenCVE AI on October 5, 2026 at 15:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 07 Oct 2026 06:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 05 Oct 2026 15:00:00 +0000

Type Values Removed Values Added
First Time appeared Progress
Progress telerik Fiddler Classic
Vendors & Products Progress
Progress telerik Fiddler Classic

Mon, 05 Oct 2026 13:00:00 +0000

Type Values Removed Values Added
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.
Title HTTP Request Smuggling Vulnerability in Progress® Telerik® Fiddler® Classic
Weaknesses CWE-444
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

Progress Telerik Fiddler Classic
cve-icon MITRE

Status: PUBLISHED

Assigner: ProgressSoftware

Published:

Updated: 2026-10-06T17:51:15.128Z

Reserved: 2026-08-21T13:37:28.618Z

Link: CVE-2026-77802

cve-icon Vulnrichment

Updated: 2026-10-05T14:38:47.581Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-05T13:16:54.293

Modified: 2026-10-06T18:16:56.153

Link: CVE-2026-77802

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-05T15:15:08Z

Weaknesses
  • CWE-444

    Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')