CVE-2026-33829: Windows Snipping Tool Spoofing Vulnerability

Published Apr 14, 2026
·
Updated

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

Other sources

Windows Snipping Tool Spoofing Vulnerability

Microsoft

Affected Software

71 affected componentsFixes available
Microsoft Windows Server 2012 R2
Microsoft Windows 10=22H2
Microsoft Windows Server 2012
Microsoft Windows 10=1607
Microsoft Windows Server 2016
Microsoft Windows Server 2016
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012
Microsoft Windows 10=22H2
Microsoft Windows 10=22H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows Server 2022
Microsoft Windows 10=21H2
Microsoft Windows Server 2022
Microsoft Windows 10 1607<10.0.14393.9060
Microsoft Windows 10 1607<10.0.14393.9060
Microsoft Windows 10 1809<10.0.17763.8644
Microsoft Windows 10 1809<10.0.17763.8644
Microsoft Windows 10 21h2<10.0.19044.7184
Microsoft Windows 10 21h2<10.0.19044.7184
Microsoft Windows 10 21h2<10.0.19044.7184
Microsoft Windows 10 22h2<10.0.19045.7184
Microsoft Windows 10 22h2<10.0.19045.7184
Microsoft Windows 10 22h2<10.0.19045.7184
Microsoft Windows 11 23h2<10.0.22631.6936
Microsoft Windows 11 23h2<10.0.22631.6936
Microsoft Windows 11 24h2<10.0.26100.8246
Microsoft Windows 11 24h2<10.0.26100.8246
Microsoft Windows 11 25h2<10.0.26200.8246
Microsoft Windows 11 25h2<10.0.26200.8246
Microsoft Windows 11 26h1<10.0.28000.1836
Microsoft Windows 11 26h1<10.0.28000.1836
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.9060
Microsoft Windows Server 2019<10.0.17763.8644
Microsoft Windows Server 2022<10.0.20348.5020
Microsoft Windows Server 2022 23h2<10.0.25398.2274
Microsoft Windows Server 2025<10.0.26100.32690
Microsoft Windows Server 2016<10.0.14393.9060
10.0.14393.9060
Microsoft Windows 10=22H2
10.0.19045.7184
Microsoft Windows Server 2012<6.2.9200.26026
6.2.9200.26026
Microsoft Windows Server 2012 R2<6.3.9600.23132
6.3.9600.23132
Microsoft Windows Server 2012<6.2.9200.26026
6.2.9200.26026
Microsoft Windows 10=22H2
10.0.19045.7184
Microsoft Windows 10=22H2
10.0.19045.7184
Microsoft Windows Server 2016<10.0.14393.9060
10.0.14393.9060
Microsoft Windows Server 2012 R2<6.3.9600.23132
6.3.9600.23132
Microsoft Windows 10=21H2
10.0.19044.7184
Microsoft Windows 10=1607
10.0.14393.9060
Microsoft Windows 11=26H1
10.0.28000.1836
Microsoft Windows 10=21H2
10.0.19044.7184
Microsoft Windows Server 2022<10.0.20348.5020
10.0.20348.5020
Microsoft Windows 11=26H1
10.0.28000.1836
Microsoft Windows Server 2022<10.0.20348.5020
10.0.20348.5020
Microsoft Windows 10=21H2
10.0.19044.7184
Microsoft Windows 11=23H2
10.0.22631.6936
Microsoft Windows Server 2025<10.0.26100.32690
10.0.26100.32690
Microsoft Windows 10=1607
10.0.14393.9060
Microsoft Windows 11=24H2
10.0.26100.8246
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.2274
10.0.25398.2274
Microsoft Windows 11=24H2
10.0.26100.8246
Microsoft Windows 11=25H2
10.0.26200.8246
Microsoft Windows 11=23H2
10.0.22631.6936
Microsoft Windows 11=25H2
10.0.26200.8246
Microsoft Windows Server 2025<10.0.26100.32690
10.0.26100.32690
Microsoft Windows Server 2019<10.0.17763.8644
10.0.17763.8644
Microsoft Windows 10=1809
10.0.17763.8644
Microsoft Windows Server 2019<10.0.17763.8644
10.0.17763.8644
Microsoft Windows 10=1809
10.0.17763.8644

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.9060Patch KB5082198
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.26026Patch KB5082127
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.7184Patch KB5082200
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.23132Patch KB5082126
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.7184Patch KB5082200
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.28000.1836Patch KB5083768
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.5020Patch KB5082142
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.6936Patch KB5082052
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.32690Patch KB5082063
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.8246Patch KB5083769
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.25398.2274Patch KB5082060
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26200.8246Patch KB5083769
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.8644Patch KB5082123

Event History

Apr 14, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
CVE Published
via MITRE·04:58 PM
Data Sourced
via MITRE·04:58 PM
DescriptionSeverity
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeaknessAffected Software
May 15, 2026
Exploit Published
via ExploitDB·12:00 AM
Known Exploited
02:51 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33829?

The severity of CVE-2026-33829 is rated as moderate due to its potential for spoofing attacks and exposure of sensitive information.

2

How do I fix CVE-2026-33829?

To fix CVE-2026-33829, apply the relevant security patches provided by Microsoft for affected Windows products.

3

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

CVE-2026-33829 affects multiple versions of Windows, including Windows Server 2012, Windows 10 (22H2, 21H2, 1809), and Windows 11.

4

What type of vulnerability is CVE-2026-33829?

CVE-2026-33829 is identified as a spoofing vulnerability in the Windows Snipping Tool.

5

Can CVE-2026-33829 be exploited remotely?

Yes, CVE-2026-33829 can be exploited over a network, allowing unauthorized actors to perform spoofing.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203