CVE-2026-32183
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 · uneditedImproper neutralization of special elements used in a command ('command injection') in Windows Snipping Tool allows an unauthorized attacker to execute code 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 confidenceA command injection vulnerability exists in Windows Snipping Tool where improper neutralization of special elements allows an unauthorized attacker to execute arbitrary code locally. This stems from the application failing to sanitize input before passing it to system commands.
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.14393.9060< 10.0.17763.8644< 10.0.19044.7184< 10.0.19045.7184< 10.0.22631.6936< 10.0.26100.8246< 10.0.26200.8246< 10.0.28000.1836CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 the installed Snipping Tool versionOpen PowerShell and run: (Get-ItemProperty 'C:\Windows\System32\SnippingTool.exe' -ErrorAction SilentlyContinue).VersionInfo.FileVersionAffected if The returned version is lower than the threshold for your Windows build (see version ranges in CVE)
-
Check Windows build numberOpen PowerShell and run: [System.Environment]::OSVersion.Version.BuildAffected if The build number matches an affected version range AND the Snipping Tool version is below the corresponding threshold
-
Verify Snipping Tool package version via PowerShellRun: Get-AppxPackage *Snip* | Select-Object Name, Version, PackageFullNameAffected if The version displayed is lower than the threshold for your Windows version as listed in the affected products
-
Confirm Snipping Tool executable existsCheck if C:\Windows\System32\SnippingTool.exe exists using: Test-Path 'C:\Windows\System32\SnippingTool.exe'Affected if The file exists and its version, when checked in step 1, is below the vulnerable threshold for your Windows build
-
Check for new Snipping Tool (Screen Sketch)Run: Get-AppxPackage *ScreenSketch* | Select-Object Name, VersionAffected if The Screen Sketch app version is below the threshold AND the legacy Snipping Tool is also present and vulnerable
-
Review Windows Update historyOpen Settings > Windows Update > Update History and look for recent Snipping Tool or Windows Security updatesAffected if No recent security updates addressing this vulnerability have been installed
A user is affected if their Windows build falls within an affected range AND the Snipping Tool version is below the specified threshold for that build.
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.14393.906010.0.17763.864410.0.19044.7184
Apply Microsoft security updates for Windows Snipping Tool once released. Until then, restrict user permissions and monitor for suspicious processes spawned from the Snipping Tool.
Windows 10 1607: build 10.0.14393.9060 | Windows 10 1809: build 10.0.17763.8644 | Windows 10 21h2: build 10.0.19044.7184 | Windows 10 22h2: build 10.0.19045.7184 | Windows 11 23h2: build 10.0.22631.6936 | Windows 11 24h2: build 10.0.26100.8246 | Windows 11 25h2: build 10.0.26200.8246 | Windows 11 26
- Open Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest security updates
- After updates install, verify the Windows build number matches or exceeds the fixed version for your Windows release
- Alternatively, manually update by searching for the specific KB patch for this vulnerability via Windows Update catalog
- Confirm Snipping Tool version is updated by checking Microsoft Store for updates or running Windows Update again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32183 — 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-32183 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