CVE-2025-55690
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 · uneditedUse after free in Windows PrintWorkflowUserSvc 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 confidenceUse after free vulnerability in Windows PrintWorkflowUserSvc that allows a locally authenticated attacker to elevate privileges to SYSTEM or other elevated contexts through exploitation of the memory corruption flaw.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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.
-
Identify Windows edition and versionRun 'winver' or check System Properties to determine if the system is Windows 11 24h2, Windows 11 25h2, or Windows Server 2025Affected if The system is not one of these editions or versions
-
Check installed build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and note the full build number (e.g., 10.0.26100.xxxx)Affected if For Windows 11 24h2 or Server 2025: build < 10.0.26100.6899. For Windows 11 25h2: build < 10.0.26200.6899
-
Verify PrintWorkflowUserSvc service statusRun 'Get-Service PrintWorkflowUserSvc' in PowerShell or check Services.msc for the PrintWorkflowUserSvc serviceAffected if The service exists and is running (vulnerability requires this service to be active)
-
Confirm security update installationCheck Windows Update history or run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"}' to verify if the CVE-2025-55690 patch is installedAffected if The security update for CVE-2025-55690 is NOT installed and the build version falls within the affected range
A system is affected if it runs Windows 11 24h2, 25h2, or Server 2025 with a build version below the patched thresholds AND the PrintWorkflowUserSvc service is present and running.
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
Deploy the Microsoft security update for CVE-2025-55690 via Windows Update or enterprise patch management systems; verify successful installation and confirm PrintWorkflowUserSvc functions normally post-patch.
Windows 11 24h2: build 10.0.26100.6899 or later | Windows 11 25h2: build 10.0.26200.6899 or later | Windows Server 2025: build 10.0.26100.6899 or later
- Open Settings > Windows Update and check for available updates
- Apply any security updates labeled for this CVE or general Windows security patches
- Restart the system when prompted to complete the update installation
- Verify the update was successful by checking the Windows version (winver command) - ensure build number is 10.0.26100.6899 or higher for Windows 11 24h2/Server 2025, or 10.0.26200.6899 or higher for Windows 11 25h2
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55690 — 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-55690 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