vciy

CVE-2021-36942

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Windows LSA Spoofing Vulnerability

CVE-2021-369424 of 4 sources documented this
65

rank 65 = 40 + 13 + 0 + 6 + 6

rank@v1 · this cycle

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.66023 · CISA KEV listed  ·  without this subject the record ranks 25

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.0, from NVD  ·  without this subject the record ranks 52

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 65

How much of the world it touches

NVD CPE configurations

6 products in the CPE ranges  ·  without this subject the record ranks 59

Someone else already set the date

CISA KEV remediation due date

CISA remediation date held  ·  without this subject the record ranks 59

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.02Mover the next 30 days, if this record is yours
Movement+$154,000on 2025-11-21, the last material move, 9 months before this reading
Basisassumeda published average, not your estate

$2.02M = $4.99M incident cost x 0.6121449559255632 exposure x 0.66023 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.66023EPSSKEV · LISTED
Severity7.5 HIGHreceipt
Harmunauthenticated · network · ransomware-linkedreceipt
Exploitationransomware use knownreceipt
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 81 days at 0.66, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
Microsoft7.5 HIGHreceipt
NVD5 MEDIUMreceipt
Scoring standard
MicrosoftCVSS v3.1receipt
NVDCVSS v2.0receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running Microsoft Windows Server 2008 R2 Service…? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classNo CWE mapping in held sources.
Ransomware campaign useKnown (CISA)receipt

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in6.1.7601.25685; 6.0.6003.21192; 6.2.9200.23435; 6.3.9600.20094; 10.0.14393.4583; 10.0.17763.2114; 10.0.19041.1165; 10.0.19042.1165receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
CISA remediation statusoverdue since 2021-11-17receipt
CISA required actionApply updates per vendor instructions.receipt
Published to CISA KEV83 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Ransomware campaign use known, 2021-11-03.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed2021-11-03receipt
  • RUNG 4Ransomware campaign use known2021-11-03receipt

Authority who says so

CVSS, the CNA7.5 HIGHreceipt
CVSS, NVD5 MEDIUMreceipt
Exploit probability0.66023 · top 0.76% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes68 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Windows Server 2008 R2 Service Pack 1; Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation); Microsoft Windows Server 2008 Service Pack 2…receipt
Published rangesmicrosoft windows server 2004 < 10.0.19041.1165; microsoft windows server 2008 r2; microsoft windows server 2012 r2; microsoft windows server 2016 < 10.0.14393.4583receipt
Show all 6 published ranges
microsoft windows server 2004 < 10.0.19041.1165
microsoft windows server 2008 r2
microsoft windows server 2012 r2
microsoft windows server 2016 < 10.0.14393.4583
microsoft windows server 2019 < 10.0.17763.2114
microsoft windows server 20h2 < 10.0.19042.1165
Fixed in6.1.7601.25685; 6.0.6003.21192; 6.2.9200.23435; 6.3.9600.20094; 10.0.14393.4583; 10.0.17763.2114; 10.0.19041.1165; 10.0.19042.1165receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Windows LSA Spoofing Vulnerability receipt

NVD's analysis a second authority

severity
5 AV:N/AC:L/Au:N/C:N/I:P/A:N
affected versions
microsoft windows server 2004 < 10.0.19041.1165; microsoft windows server 2008 r2; microsoft windows server 2012 r2; and 3 more, listed in full below
also scored by
[email protected] 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N · [email protected] 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

The CNA scored it 7.5 and NVD 5. Both are shown because both were published; we do not pick one.

check it yourself msrc.microsoft.com receipt

Dated events

2021-11-03Added to CISA KEV2021-11-17CISA remediation due2022-01-06EPSS moved 0.07 to 0.242023-03-07EPSS moved 0.26 to 0.902026-06-15EPSS moved 0.94 to 0.66

Movement the material steps

13 Aug 20210.00416
6 Jan 20220.24372 · crossed 0.10
4 Feb 20220.13392
5 Feb 20220.65667 · crossed 0.50
1 Apr 20220.26327 · crossed 0.50
7 Mar 20230.90369 · crossed 0.50 and 0.90 · scoring model v2023.03.01
3 Apr 20230.89293 · crossed 0.90
29 Jun 20230.77673
6 Oct 20230.88670
28 Sep 20240.78107
17 Dec 20240.88252
17 Mar 20250.93533 · crossed 0.90 · scoring model v2025.03.14
18 Nov 20250.88781 · crossed 0.90
21 Nov 20250.93809 · crossed 0.90
15 Jun 20260.66023 · crossed 0.90 · scoring model v2026.06.15
3 Aug 20260.66023

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 57 observations
13 Aug 20210.00416
21 Aug 20210.04557
7 Oct 20210.06701
6 Jan 20220.24372
4 Feb 20220.13392
5 Feb 20220.65667
1 Apr 20220.26327
7 Mar 20230.90369
20 Mar 20230.90633
3 Apr 20230.89293
17 Apr 20230.88993
8 May 20230.82550
17 May 20230.83259
1 Jun 20230.81199
29 Jun 20230.77673
8 Jul 20230.85864
28 Jul 20230.86735
9 Aug 20230.85758
8 Sep 20230.83794
22 Sep 20230.84726
6 Oct 20230.88670
16 Nov 20230.86357
29 Dec 20230.84780
21 Feb 20240.86554
18 Mar 20240.85287
27 Apr 20240.81552
4 Jul 20240.83042
18 Jul 20240.81035
31 Jul 20240.79356
15 Aug 20240.81633
14 Sep 20240.81470
28 Sep 20240.78107
13 Oct 20240.80209
13 Nov 20240.81281
28 Nov 20240.78315
15 Dec 20240.78600
17 Dec 20240.88252
30 Dec 20240.81407
15 Jan 20250.83219
1 Feb 20250.85285
19 Feb 20250.87253
9 Mar 20250.84629
17 Mar 20250.93533
8 May 20250.93623
24 May 20250.93632
30 May 20250.93623
22 Jun 20250.93632
11 Oct 20250.93795
22 Oct 20250.93809
18 Nov 20250.88781
21 Nov 20250.93809
16 Dec 20250.93551
11 Apr 20260.93727
8 Jun 20260.93551
15 Jun 20260.66023
21 Jul 20260.65543
3 Aug 20260.66023

57 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.66023Published2021-08-12CISA KEV2021-11-03Index as of2026-09-04

Listed by CISA 83 days after it published, exploit probability more than doubled between 2022-02-04 and 2022-02-05 (0.13392 → 0.65667) and the record had been public for 5 years when this index was last written.

No material movement in 32 days as of the last ingest this index recorded.

Published 2021-08-12 receipt · CISA KEV 2021-11-03 receipt · Index as of 2026-09-04 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2021-36942.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.