# CVE-2026-33829: Windows Snipping Tool Spoofing Vulnerability

> An attacker can spoof the Windows Snipping Tool to expose sensitive information to unauthorized actors over a network.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-wmq5-p9j9-jfgx

## What is CVE-2026-33829?

CVE-2026-33829 is a medium-severity vulnerability in Microsoft Windows 10 1607, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Exposure of sensitive information to an unauthorized actor in Windows Snipping Tool allows an unauthorized attacker to perform spoofing over a network.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-33829?

It affects 14 products.


Products: Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 23h2, Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows 11 26h1, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2026-33829?

No fix has been published for CVE-2026-33829 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33829 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33829 exists.

Public exploit code:

- Windows Snipping Tool - NTLMv2 Hash Hijack (exploitdb)
- Vulnerability Case Study: CVE-2026-33829 (Windows Snipping Tool NTLM Coercion) (github_poc): https://github.com/rahultb-sec/CVE-2026-33829-Writeup
- https://github.com/seguridadentrerios/CVE-2026-33829 (github_poc): https://github.com/seguridadentrerios/CVE-2026-33829

## Other vulnerabilities in Microsoft Windows 10 1607

- [CVE-2026-33824](https://insights.sbomify.com/CVE-2026-33824/): Microsoft Internet Key Exchange (IKE) Service Extensions Double Free (critical 9.8, exploited in the wild)
- [CVE-2026-21510](https://insights.sbomify.com/CVE-2026-21510/): Microsoft Windows Shell Protection Mechanism Failure (high 8.8, exploited in the wild)
- [CVE-2026-21513](https://insights.sbomify.com/CVE-2026-21513/): Microsoft MSHTML Framework Protection Mechanism Failure (high 8.8, exploited in the wild)
- [CVE-2023-32049](https://insights.sbomify.com/CVE-2023-32049/): Microsoft Windows Defender SmartScreen Security Feature Bypass (high 8.8, exploited in the wild)
- [CVE-2023-29360](https://insights.sbomify.com/CVE-2023-29360/): Microsoft Streaming Service Untrusted Pointer Dereference (high 8.4, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33829 and fix it if it is affected.

What it is: CVE-2026-33829 is a medium-severity vulnerability in Microsoft Windows 10 1607, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33829 exists.

Affected product: Microsoft Windows 10 1607. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33829/ (Markdown: https://insights.sbomify.com/CVE-2026-33829/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33829
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33829
- OSV: https://osv.dev/vulnerability/CVE-2026-33829

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33829/
Summaries are generated and may contain mistakes; the official description above is the record.