Skip to main content

Fiddler Classic EUVDEUVD-2026-92427

| CVE-2026-77804 MEDIUM
Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)
2026-10-05 ProgressSoftware GHSA-rx7m-qprj-p54h
6.6
CVSS 3.1 · Vendor: ProgressSoftware
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain low-privileged local shell on host
  2. Delivery
    Monitor user-writable temp certificate path
  3. Exploit
    Victim initiates Fiddler cert trust and approves UAC
  4. Execution
    Swap staged cert in TOCTOU window
  5. Persist
    Elevated helper imports attacker root CA
  6. Impact
    Intercept and modify machine-wide TLS traffic

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture TOCTOU prevention
Exploitation Conditions

Exploitation requires: (1) the attacker already has local low-privileged code execution on the same Windows host; (2) a legitimate user must actively initiate Fiddler Classic's HTTPS-decryption root-certificate trust operation AND approve the UAC elevation prompt for the TrustCert helper; and (3) the attacker must win the TOCTOU race by replacing Fiddler's certificate file in its user-writable temp location between write and the elevated helper's read. Limiting factors that reduce real-world risk: it is local-only (no remote vector), depends on a specific one-time user-triggered workflow, needs mandatory user approval of elevation, and success is probabilistic because it hinges on timing the race window. Affects Fiddler Classic for Windows versions prior to v6.0.20262.10021.

Impact

This is a genuine but conditional local privilege-abuse flaw, not an internet-facing emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N, base 6.6) confirms a LOCAL attack vector requiring an already-authenticated low-privileged user on the machine plus user interaction, which caps real-world urgency well below a remote/unauthenticated bug of the same impact. No EPSS score, no KEV listing, and no POC were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation - EPSS/KEV absence here is a true information gap, not confirmation of safety. The C:H/I:H rating is well justified: a successfully planted root CA in the Local Computer Trusted Root store enables full TLS interception/modification for every user on the host. I disagree with the input AC:L: winning a time-of-check-to-time-of-use race on a temp file is not reliably reproducible and realistically warrants AC:H, which would lower the score slightly. Net: a legitimate medium-severity local issue to patch on developer/QA endpoints, but it should not be triaged alongside remotely exploitable critical CVEs.

Exploit ScenarioDerived

A low-privileged user already logged onto a shared or multi-user Windows workstation monitors the user-writable temp location where Fiddler stages its root certificate. When a legitimate user initiates Fiddler's HTTPS decryption setup and approves the UAC elevation prompt, the attacker swaps the staged certificate for their own in the TOCTOU window, and the elevated TrustCert helper imports the attacker's CA into the machine-wide Trusted Root store. No public exploit code is identified at time of analysis, and the attacker must both win the race and rely on the victim approving elevation.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 05, 2026

Local privilege abuse in Progress Telerik Fiddler Classic for Windows (versions prior to v6.0.20262.10021) lets a low-privileged local attacker plant an attacker-controlled root certificate in the machine's Trusted Root Certification Authorities store by winning a TOCTOU race during Fiddler's one-time HTTPS-decryption certificate trust workflow. The attacker must already have code execution on the host, the legitimate user must initiate the trust operation and approve the UAC elevation prompt, and the substitution of Fiddler's temporary certificate file must land in the narrow window between write and the elevated TrustCert helper's read. No public exploit code has been identified at time of analysis and the flaw is local-only with no remote vector, so this is a conditional, probabilistic privilege-abuse issue rather than an internet-facing emergency.

RemediationAI

Vendor-released patch: upgrade Fiddler Classic for Windows to v6.0.20262.10021 or later, which closes the race by removing or hardening the user-writable staging step in the certificate trust flow; consult the Progress Telerik advisory at https://docs.telerik.com/fiddler/knowledge-base/kb-security-root-certificate-installation-toctou-cve-2026-77804 for the exact installer and any rollout guidance. If immediate upgrade is not possible, compensating controls should target the two prerequisites the attacker needs. First, tighten filesystem permissions on Fiddler's temporary/staging directory so that low-privileged local accounts cannot write or replace files there - this breaks the substitution step, at the cost of possible interoperability issues if the helper expects a permissive temp path, so validate the HTTPS-decryption workflow after the change. Second, treat the certificate trust prompt as a privileged action: only perform the one-time root-certificate installation on hosts where all local accounts are trusted, or perform it from an isolated administrative session or dedicated VM, and never approve the UAC prompt on a shared or multi-user workstation where an untrusted local user could be racing the operation. Additionally, audit the Local Computer Trusted Root Certification Authorities store for unexpected or duplicate root certificates after any Fiddler certificate installation, and consider restricting Fiddler usage on high-value hosts until the patched build is deployed. Because exploitation requires pre-existing local code execution, host-level detection and containment of local attacker footholds remains the most effective secondary defense.

Affected VersionsENISA

Progress® Telerik® Fiddler® Classic 1.0.0 <6.0.20262.10021

Affected Packages

euvd progress_telerik_fiddler_classic fix: 6.0.20262.10021

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-367 (time-of-check time-of-use race condition) in Fiddler Classic's certificate installation logic. When a user enables HTTPS decryption, Fiddler generates its interception root certificate, writes it to a temporary file in a user-writable location, and then invokes the external TrustCert helper, which requests UAC elevation and imports the certificate into the Local Computer\Trusted Root Certification Authorities certificate store. Because the file is written before elevation and read after elevation, the file's contents are effectively re-resolved at a later time than their initial validation/write - the classic TOCTOU gap. A local attacker who can write to that staging path can swap the file during the interval, so the elevated helper imports the attacker's certificate instead of Fiddler's. Once a rogue root is trusted at machine scope, the attacker can transparently man-in-the-middle, decrypt, and modify TLS traffic from any user or service on that host, which drives the High confidentiality and High integrity impact; availability is unaffected and the scope remains unchanged. The vendor scores the race as low complexity (AC:L) for a base of 6.6, while independent analysis treats successful timing as high complexity (AC:H) given the mandatory user-initiated workflow and elevation approval; the vector is local (AV:L) with low privileges required (PR:L), meaning the attacker already needs an existing foothold on the same Windows machine, and user interaction (UI:R) is required.

Know when Progress Telerik Fiddler Classic gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ProgressSoftware) PRIMARY 6.6 MEDIUM
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
vuln.today AI 6.0 MEDIUM

Local attacker with existing low privileges (AV:L/PR:L); AC:H because success depends on winning a non-deterministic TOCTOU race; UI:R as the victim must trigger and approve elevation; machine-wide TLS interception gives C:H/I:H, no availability impact.

3.1 AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N
4.0 AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ProgressSoftware).

CVSS VectorVendor: ProgressSoftware

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

2
Patch available
Oct 05, 2026 - 14:01 EUVD
CVE Published
Oct 05, 2026 - 12:40 cve.org
MEDIUM 6.6

DescriptionCVE.org

In Progress® Telerik® Fiddler® Classic for Windows, versions prior to v6.0.20262.10021, a time-of-check time-of-use (TOCTOU) race condition exists in the installation of the HTTPS interception root certificate into the Local Computer certificate store. Fiddler writes the certificate to a temporary file in a user-writable location and then launches the external TrustCert helper application, which elevates and imports the certificate from that file. A local threat actor with low privileges who replaces the temporary file between the time it is written and the time the elevated helper reads it can cause an attacker-supplied root certificate to be installed in the Local Computer Trusted Root Certification Authorities store, enabling subsequent interception and modification of TLS-protected traffic on the machine. Successful exploitation requires the user to initiate the certificate trust operation and approve the elevation prompt.

Threat Intelligence Overview

EPSS Score
0.1%
Top 100% exploitable
Prevalence
Medium
popular developer/QA web-debugging proxy, common on dev endpoints not servers
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

33
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +33
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy