CVE-2025-49722
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 · uneditedUncontrolled resource consumption in Windows Print Spooler Components allows an authorized attacker to deny service over an adjacent network.
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 confidenceUncontrolled resource consumption vulnerability in Windows Print Spooler Components allows an authenticated attacker on an adjacent network to cause denial of service by exhausting system resources.
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.10240.21073< 10.0.14393.8246< 10.0.17763.7558< 10.0.19044.6093< 10.0.19045.6093< 10.0.22621.5624< 10.0.22631.5624< 10.0.26100.4652CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Verify Print Spooler service is runningOpen Services console (services.msc) or run 'Get-Service Spooler' in PowerShell to check if the Print Spooler service is runningAffected if The service is running - this is the vulnerable component that must be active for exploitation
-
Identify Windows version and build numberRun 'winver' from Run dialog, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt, or use PowerShell '[System.Environment]::OSVersion.Version'Affected if The version displayed is within any of the affected Windows 10 or Windows 11 release ranges listed in the CVE
-
Confirm exact build version for comparisonRun 'winver' or check Settings > System > About to see the full Windows build number (e.g., 10.0.19045.xxxx)Affected if The build number is lower than the patched versions: 10240.21073 (1507), 14393.8246 (1607), 17763.7558 (1809), 19044.6093 (21h2), 19045.6093 (22h2), 22621.5624 (22h2), 22631.5624 (23h2), or 26100.4652 (24h2)
-
Check installed security updatesOpen Settings > Windows Update > Update history, or run 'Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10' in PowerShell to view recent patchesAffected if No recent Print Spooler or Windows security update matching the CVE release date is installed
A user is affected if the Print Spooler service is running AND the Windows build number is lower than the patched versions listed for their specific Windows release.
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.10240.2107310.0.14393.824610.0.17763.7558
Apply the relevant Microsoft security update for Windows Print Spooler when released; if printing is not required, consider disabling the Print Spooler service as a temporary workaround.
Install the latest Windows Security Updates for your respective Windows 10 or 11 version from Windows Update or Microsoft Update Catalog. The fixed builds are listed in the affected versions (e.g., Windows 10 22h2 requires 10.0.19045.6093 or later).
- Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Open Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install all available updates
- Ensure the installed build number meets or exceeds the fixed version for your Windows release: Windows 10 1507: 10.0.10240.21073, Windows 10 1607: 10.0.14393.8246, Windows 10 1809: 10.0.17763.7558, Windows 10 21h2: 10.0.19044.6093, Windows 10 22h2: 10.0.19045.6093, Windows 11 22h2: 10.0.22621.5624, Windows 11 23h2: 10.0.22631.5624, Windows 11 24h2: 10.0.26100.4652
- Restart the computer after updates are installed
- Verify the update was applied by checking Windows Update history or running 'winver' again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49722 — 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-49722 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