CVE-2026-50383
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 · uneditedBuffer over-read in Windows Print Spooler Components allows an authorized attacker to disclose information locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 buffer over-read vulnerability in Windows Print Spooler Components that allows a local, authorized attacker to read sensitive information from memory due to improper bounds checking. The flaw enables information disclosure without requiring elevated privileges.
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.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269< 10.0.28000.2525< 10.0.17763.9020< 10.0.20348.5386CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 version and build numberOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'. Alternatively, run 'ver' command or check Registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersionAffected if The installed Windows build number falls below the threshold for your specific version (e.g., below 10.0.17763.9020 for Windows 10 1809/Server 2019, below 10.0.19044.7548 for Windows 10 21h2, etc.)
-
Verify Print Spooler service statusOpen Services console (services.msc) or run 'Get-Service Spooler' in PowerShell to check if the Print Spooler service exists and its current running stateAffected if The Print Spooler service (Spooler) is installed and running on the system, making the vulnerable component active
-
Confirm Print Spooler is accessible to non-privileged usersCheck service configuration by running 'sc qc Spooler' or reviewing service permissions. Also verify non-administrator users have print privileges via 'net localgroup "Users"' or check if standard users can submit print jobsAffected if Non-administrative users have the ability to interact with the Print Spooler service, which is required for exploitation as the vulnerability allows information disclosure without elevated privileges
Your system is affected if it runs a Windows version with a build number lower than the thresholds listed AND has the Print Spooler service accessible to non-privileged users.
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.17763.902010.0.19044.754810.0.19045.7548
Apply the relevant Microsoft security update for Windows Print Spooler Components. For systems where patching is delayed, consider restricting non-administrative users from interacting with the Print Spooler service and monitoring for unusual print service activity.
Install Windows security update for Print Spooler Components matching your Windows version (versions listed in steps)
- Open Settings > Update & Security > Windows Update
- Click 'Check for updates' to install any available security updates
- After updates install, verify the installed version by running 'winver' command
- Confirm the version meets or exceeds the fixed version for your Windows release: Windows 10 1809/Server 2019: 10.0.17763.9020, Windows 10 21h2: 10.0.19044.7548, Windows 10 22h2: 10.0.19045.7548, Windows 11 24h2: 10.0.26100.8875, Windows 11 25h2: 10.0.26200.8875, Windows 11 26h1: 10.0.28000.2525, Windows Server 2022: 10.0.20348.5386
- Restart the system if prompted to complete the update installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50383 — 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-2026-50383 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