CVE-2022-30226
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 · uneditedWindows Print Spooler Elevation of Privilege Vulnerability
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 confidenceWindows Print Spooler Elevation of Privilege vulnerability allowing a local attacker to gain higher system privileges. The Print Spooler service contains a flaw that can be exploited to escalate from low-privileged user to SYSTEM or administrator-level access.
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 dataall versions= 20h2= 21h1= 21h2= 1607= 1809all versionsall versionsall versionsall versionsall versions= r2all versions= r2all versions= 20h2CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Confirm Windows version is within affected rangeRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to check the installed Windows versionAffected if The version matches Windows 10 (1607, 1809, 20h2, 21h1, 21h2), Windows 11, Windows 7, Windows 8.1, Windows Rt 8.1, or Windows Server 2008/2012/2016 as listed in the affected products
-
Check if Print Spooler service is runningRun 'Get-Service Spooler' in PowerShell or 'sc query spooler' in Command PromptAffected if The Print Spooler service status is Running - this is required for the vulnerability to be exploitable
-
Verify if the security update is installedRun 'Get-HotFix -Id "KB5014702"' in PowerShell or 'wmic qfe list | findstr "KB5014702"' to check for the CVE-2022-30226 patchAffected if The KB5014702 update is NOT listed among installed hotfixes, meaning the security patch is missing
A user is affected if they are running an affected Windows version, the Print Spooler service is enabled/running, and the KB5014702 security update is not installed.
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 · scopedApply Microsoft security updates for CVE-2022-30226. If the Print Spooler service is not required, consider disabling it or blocking related RPC/TCP ports (135, 139, 445) at the network perimeter as a defense-in-depth measure.
- Check for and apply the latest Windows security updates from Windows Update or Microsoft Update Catalog
- For enterprise deployments, deploy the appropriate Microsoft Security Update (KB) for your specific Windows version
- After patching, verify the Print Spooler service is running properly and printers are accessible
- Validate that the vulnerability is mitigated by confirming the patch version matches the Microsoft Security Response Center release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30226 — 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-2022-30226 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