Skip to main content
Mallory
MediumExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2021-31955: Windows Kernel SuperFetch Information Disclosure

Published Jun 8, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS81.1%100th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2021-31955CWE-200

CVE-2021-31955 is an information disclosure vulnerability in the Windows kernel associated with SuperFetch. Queries through NtQuerySystemInformation using the SuperfetchPrivSourceQuery information class disclose kernel addresses of EPROCESS structures for running processes. PuzzleMaker exploited the vulnerability as a zero-day in April 2021 within a Chrome-based attack chain, pairing it with CVE-2021-31956 to support sandbox escape and privilege escalation. Microsoft patched the vulnerability on June 8, 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.

The vulnerability exposes kernel process-object addresses to an attacker with prior low-privileged access. These addresses can support exploitation of other kernel vulnerabilities. In the PuzzleMaker attacks, the disclosure was combined with CVE-2021-31956 in a chain that escaped the Chrome sandbox and obtained SYSTEM privileges; those capabilities were not provided by CVE-2021-31955 alone.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting execution of untrusted code and constraining initial access vectors that could provide a low-privileged foothold. Harden browsers and application sandbox boundaries, restrict local code execution where feasible, and monitor for suspicious use of kernel information-querying behavior in conjunction with exploit-chain activity. Because exploitation requires prior access and was observed as part of a chained attack, mitigations that prevent or detect the initial compromise materially reduce risk.

Remediation

Patch, then assume compromise.

Apply the Microsoft security updates released on June 8, 2021 that address CVE-2021-31955, or applicable superseding updates.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
forti_shieldThis repository contains a local privilege escalation exploit targeting Windows 10 20H2, specifically leveraging CVE-2021-31955, CVE-2015-4077, and CVE-2015-5736. The main exploit logic resides in 'forti_exploit.cpp', which orchestrates the attack by leaking kernel addresses, manipulating kernel memory, and ultimately stealing the SYSTEM token using custom shellcode found in 'token_stealing.asm'. The exploit is operational but not weaponized, as it relies on hardcoded offsets and is not version-independent. The exploit launches a SYSTEM-level command shell upon success. The repository includes standard C++ project files and headers, with the main entry point in 'forti_exploit.cpp'. No network endpoints are involved; the attack vector is purely local, requiring code execution on the target machine. The exploit manipulates specific files in the user's AppData directory as part of its process.ApexPredator-InfoSec · Disclosed Oct 29, 2025 · cpp · assembly · localOperationalCVE-2021-31955-POCThis repository contains a proof-of-concept (POC) exploit for CVE-2021-31955, a Windows kernel information disclosure vulnerability. The main code is in 'CVE-2021-31955/CVE-2021-31955.cpp', which demonstrates how to use the undocumented SystemSuperfetchInformation class with NtQuerySystemInformation to leak kernel EPROCESS addresses for running processes. The exploit is local and requires execution on a vulnerable, unpatched 64-bit Windows system. The project includes standard Visual Studio files for building the application, as well as headers and a README describing the vulnerability and expected output. The exploit does not provide code execution or privilege escalation, but demonstrates kernel address disclosure, which can be used to bypass kernel ASLR in further attacks.freeide · Disclosed Jun 26, 2021 · c++ · localPoC
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 1809operating_system
Microsoft CorporationWindows 10 1909operating_system
Microsoft CorporationWindows 10 2004operating_system
Microsoft CorporationWindows 10 20h2operating_system
Microsoft CorporationWindows 10 21h1operating_system
Microsoft CorporationWindows Server 2004operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 20h2operating_system
FAQ

Frequently asked questions

Is CVE-2021-31955 exploited in the wild?
Yes. As of Oct 16, 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-31955?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2021-31955, the earliest disclosed Jun 26, 2021.
Is there a patch for CVE-2021-31955?
Apply the Microsoft security updates released on June 8, 2021 that address CVE-2021-31955, or applicable superseding updates.
What products are affected by CVE-2021-31955?
Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 1909, Microsoft Corporation Windows 10 2004, Microsoft Corporation Windows 10 20h2, Microsoft Corporation Windows 10 21h1, and 3 more.
How severe is CVE-2021-31955?
CVE-2021-31955 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 81.1% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

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

View more in app →
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 evidence3Every report linking this CVE to a named adversary.
Associated malwareMalware 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 activityCommunity discussion across Reddit, Mastodon, and other social sources.