Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2021-31979: Windows Kernel Integer Overflow Privilege Escalation

Published Jul 14, 2021 · Updated 20 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS7.8High · v3.1
EPSS4.5%92nd percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2021-31979CWE-190

CVE-2021-31979 is an integer overflow vulnerability in the Windows NT operating system kernel that can lead to a buffer overflow and local privilege escalation. Successful exploitation can allow an attacker to escape a browser sandbox and execute code in kernel mode. Candiru, tracked by Microsoft as SOURGUM, exploited the vulnerability as a zero-day in browser-and-Windows exploit chains used to deploy DevilsTongue spyware. Microsoft patched the vulnerability on July 13, 2021.

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 compromises the Windows privilege boundary, enabling kernel-mode code execution with high impact to system confidentiality, integrity, and availability. In observed exploit chains, it supported browser sandbox escape and installation of privileged spyware. Subsequent DevilsTongue capabilities included credential theft, file exfiltration, and access to messaging data.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting opportunities for attackers to obtain initial code execution on endpoints, especially through browsers and messaging-delivered exploit chains; enforce least privilege for users; harden and monitor browser sandbox escape activity; and use endpoint protections capable of detecting exploit chains and blocking post-exploitation components. Where available, deploy attack surface reduction controls and EDR detections to identify suspicious privilege-escalation behavior. These measures are compensating controls only and do not replace installing the vendor fix.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update addressing CVE-2021-31979 for the affected Windows version, released on July 13, 2021, or an applicable superseding update. Use the Microsoft Security Update Guide to identify the appropriate update for each system.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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 10operating_system
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 1909operating_system
Microsoft CorporationWindows 10 2004operating_system
Microsoft CorporationWindows 10 20h2operating_system
Microsoft CorporationWindows 10 21h1operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 2004operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_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 20h2operating_system
FAQ

Frequently asked questions

Is CVE-2021-31979 exploited in the wild?
Yes. As of Oct 28, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2021-31979?
As of Oct 28, 2026, Mallory has found no public exploit for CVE-2021-31979.
Is there a patch for CVE-2021-31979?
Apply the Microsoft security update addressing CVE-2021-31979 for the affected Windows version, released on July 13, 2021, or an applicable superseding update. Use the Microsoft Security Update Guide to identify the appropriate update for each system.
What products are affected by CVE-2021-31979?
Microsoft Corporation Windows 10, Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 1909, and at least 15 more.
How severe is CVE-2021-31979?
CVE-2021-31979 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 4.5% (92nd percentile) as of Oct 28, 2026.
Activity feed

Recent activity

10 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 evidence8Every report linking this CVE to a named adversary.
Associated malware7Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.