Vulnerability in Progress Telerik Fiddler Everywhere (CVE-2026-86157)
Summary
Vulnerability in Progress Telerik Fiddler Everywhere (CVE-2026-86157). Confidential information can be exposed externally.
Original description
The description as published by the source.
Exposure of privileged IPC functionality in Progress Telerik Fiddler Everywhere before version 8.2.0 allows a local, low-privileged attacker who can modify application launch parameters and persuade a user to start the application to replace the application UI or settings with attacker-controlled content. Successful exploitation could result in disclosure of OAuth authentication tokens, execution of locally accessible programs, or unauthorized modification of application-generated configuration files.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-86157 has been found in Progress Telerik Fiddler Everywhere.
Confidential information can be exposed externally. CVSS score: 5.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Progress Telerik Fiddler Everywhere CVE-2026-86157" on the vendor's site.
CVE-2026-86157 (Progress Telerik Fiddler Everywhere) — CWE-749 / CVSS v3 5.6
Attack vector: local
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-749) exists in Progress Telerik Fiddler Everywhere.
Check the vendor advisory for the affected versions of Progress Telerik Fiddler Everywhere.
Severity: Medium (CVSS 5.6/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Progress Telerik Fiddler Everywhere を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web telerik.com
- web nvd.nist.gov
- web telerik.com
- web github.com