CVE-2025-55694
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper access control in Windows Error Reporting allows an authorized attacker to elevate privileges locally.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a local privilege escalation vulnerability in Windows Error Reporting (WER) caused by improper access control. An authorized attacker with the ability to execute code locally can exploit this flaw to elevate their privileges to a higher level, potentially SYSTEM. The vulnerability stems from inadequate permission checks in how WER handles crash reports and associated file operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.26100.6899< 10.0.26200.6899< 10.0.26100.6899CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Windows build versionOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /C:"Build"' to obtain the full OS build number (e.g., 10.0.26100.xxxx)Affected if The build number is lower than 10.0.26100.6899 for Windows 11 24h2 or Server 2025, or lower than 10.0.26200.6899 for Windows 11 25h2
-
Confirm exact Windows editionRun 'systeminfo' and note the OS Name and OS Version fields to verify whether the system is Windows 11 24h2, Windows 11 25h2, or Windows Server 2025Affected if The system matches an affected edition (Windows 11 24h2, 25h2, or Server 2025) and the build falls below the respective threshold
-
Verify WER service statusOpen Services (services.msc) or run 'sc query WerSvc' in Command Prompt to check if the Windows Error Reporting service is runningAffected if The WER service is enabled and running, as the vulnerability exploits WER file handling
-
Inspect WER report folders for unauthorized accessCheck permissions on the WER report directories (typically %ProgramData%\Microsoft\Windows\WER and %LOCALAPPDATA%\Microsoft\Windows\WER) by right-clicking the folder, selecting Properties, then Security, and reviewing which users have Write or Full Control permissionsAffected if Low-privilege users have Write or Full Control permissions to WER report folders, which could allow exploitation
The system is likely affected if it runs Windows 11 24h2, 25h2, or Windows Server 2025 with a build number below the specified thresholds and has WER enabled with permissive folder permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.26100.689910.0.26200.6899
Apply the Microsoft security updates for CVE-2025-55694 as soon as they become available through Windows Update or the Microsoft Security Update Guide. Until patched, limit local user privileges and monitor for suspicious WER-related file activity.
Windows 11 24h2 build 10.0.26100.6899+ | Windows 11 25h2 build 10.0.26200.6899+ | Windows Server 2025 build 10.0.26100.6899+
- Open Windows Settings and navigate to Windows Update
- Click 'Check for updates' to download and install the latest cumulative security update
- Ensure the installed build version is 10.0.26100.6899 or higher for Windows 11 24h2/Windows Server 2025, or 10.0.26200.6899 or higher for Windows 11 25h2
- Restart the system when prompted to complete the update installation
- Verify the update was applied by running 'winver' command to confirm the build number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55694 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data