dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Nov 2021.
Windows 10 1507Operating system · Microsoft

CVE-2021-31199

MEDIUM · 5.2 CVSS v3.1 Developing Published 2021-06-08
Fix available
A fix is available. Upgrade to 10.0.10240.18967 / 10.0.14393.4467 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft Enhanced Cryptographic Provider Elevation of Privilege Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-10.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.18967
Windows 10 1607Operating system
Affected:< 10.0.14393.4467
Windows 10 1809Operating system
Affected:< 10.0.17763.1999
Windows 10 1909Operating system
Affected:< 10.0.18363.1621
Windows 10 2004Operating system
Affected:< 10.0.19041.1052
Windows 10 20h2Operating system
Affected:< 10.0.19042.1052
Windows 10 21h1Operating system
Affected:< 10.0.19043.1052
Windows 7Operating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.18967 / 10.0.14393.4467 / 10.0.17763.1999 or later
Fixed in 10.0.10240.1896710.0.14393.446710.0.17763.1999
Vendor patch portal.msrc.microsoft.com →
Recommended fix High confidence

Windows 10 1507: 10.0.10240.18967 | Windows 10 1607: 10.0.14393.4467 | Windows 10 1809: 10.0.17763.1999 | Windows 10 1909: 10.0.18363.1621 | Windows 10 2004: 10.0.19041.1052 | Windows 10 20h2: 10.0.19042.1052 | Windows 10 21h1: 10.0.19043.1052 | Windows 7: No patch available - migrate to supported O

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows 10 systems: Navigate to Settings > Update & Security > Windows Update and check for updates
  3. Install the cumulative security update for your specific Windows 10 version (KB5001402 or later)
  4. For Windows 7 systems: Note that Windows 7 reached end of life on January 14, 2020 and no longer receives security updates; migration to a supported operating system is required
  5. After installation, restart the system to apply the security update
  6. Verify the update was applied by checking installed updates (control panel > programs > view installed updates)
Caveat Windows 7 has no security patches available; requires operating system migration

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get it fixed fast

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-31199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-31199 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data