Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-33829: NTLM Hash Disclosure in Windows Snipping Tool ms-screensketch URI Handler

Published Apr 14, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v3.1
EPSS3.6%90th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2026-33829CWE-200 · Exposure of Sensitive Information…

CVE-2026-33829 is a spoofing and information disclosure vulnerability in Microsoft Windows Snipping Tool caused by improper validation of input supplied through the application's registered ms-screensketch URI handler. The vulnerable deep-link handling logic accepts a filePath parameter and can be induced to access an attacker-controlled UNC path over SMB. When the target system attempts that remote access, Windows automatically performs NTLM authentication in the security context of the current user, exposing the user's Net-NTLMv2 authentication material to the remote server. Exploitation is typically achieved by convincing a user to open a crafted link from a web page, email, or other URL source that launches Snipping Tool with attacker-controlled parameters. The application may appear to open normally while the credential leakage occurs in the background.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation discloses the victim user's Net-NTLMv2 hash to an attacker-controlled server, resulting in loss of confidentiality. The captured authentication material can be used for NTLM relay attacks against internal services and, depending on the environment and password strength, may also support offline password cracking attempts. The vulnerability does not inherently provide direct code execution or denial of service, but it can enable follow-on authentication abuse and deeper network compromise under the victim's security context.

Mitigation

If you can’t patch tonight, do this now.

Until patching is fully deployed, reduce exposure by blocking unnecessary outbound SMB traffic, especially to untrusted networks, enforcing SMB signing to hinder relay attacks, and disabling or restricting NTLM where operationally feasible. Additional defensive measures include monitoring for unexpected outbound SMB authentication attempts and strengthening user protections against malicious links and social-engineering lures that launch URI handlers.

Remediation

Patch, then assume compromise.

Apply Microsoft's April 14, 2026 security updates that address CVE-2026-33829 in affected Windows Snipping Tool deployments. Organizations should ensure all affected Windows 10, Windows 11, and supported Windows Server systems receiving Snipping Tool updates are brought to the patched level through normal patch management processes.

Public exploits

Exploits

No validated public exploits yet. Hidden: 4 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

Frequently asked questions

Is CVE-2026-33829 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-33829 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-33829?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-33829.
Is there a patch for CVE-2026-33829?
Apply Microsoft's April 14, 2026 security updates that address CVE-2026-33829 in affected Windows Snipping Tool deployments. Organizations should ensure all affected Windows 10, Windows 11, and supported Windows Server systems receiving Snipping Tool updates are brought to the patched level through normal patch management processes.
What products are affected by CVE-2026-33829?
Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, Microsoft Corporation Windows 11 23h2, and 11 more.
How severe is CVE-2026-33829?
CVE-2026-33829 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 3.6% (90th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+4 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity23Community discussion across Reddit, Mastodon, and other social sources.