CVE-2025-53133
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 · high confidenceUse after free vulnerability in Windows PrintWorkflowUserSvc allows a local authorized attacker to exploit memory corruption and elevate privileges to higher integrity levels.
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.4851< 10.0.26100.4851CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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 version and build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to confirm the system is Windows 11 24h2 or Windows Server 2025Affected if System is Windows 11 24h2 or Windows Server 2025 with build < 26100.4851
-
Check installed Windows build versionRun 'winver' or 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildNumber' and compare to 26100.4851Affected if Build number is lower than 26100.4851 (specifically below 10.0.26100.4851)
-
Verify PrintWorkflowUserSvc service statusRun 'sc query PrintWorkflowUserSvc' to check if the Print Workflow User Service exists and is configured on the systemAffected if The PrintWorkflowUserSvc service is present and enabled on the system
-
Check if PrintWorkflowUserSvc is currently runningRun 'sc queryex PrintWorkflowUserSvc' or check via Services.msc to see if the service is in a running stateAffected if The PrintWorkflowUserSvc service is currently running - the vulnerability requires the service to be active for exploitation
The system is affected if it is Windows 11 24h2 or Windows Server 2025 with a build version lower than 10.0.26100.4851 AND the PrintWorkflowUserSvc service is present on the system.
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.4851
Apply Microsoft security updates for this vulnerability via Windows Update or enterprise patch management, and verify the PrintWorkflowUserSvc is running with appropriate service account permissions.
Windows 11 24h2 build 10.0.26100.4851 or later | Windows Server 2025 build 10.0.26100.4851 or later
- Open Settings > Windows Update and check for updates to install the security patch
- Alternatively, run 'winver' in Run dialog to check current build number
- If build is below 10.0.26100.4851, install Cumulative Update via Windows Update or download from Microsoft Update Catalog
- Restart the computer when prompted to complete the update
- Verify the fix by running 'winver' and confirming build 10.0.26100.4851 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53133 — 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-53133 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