CVE Intelligence
CISA KEV Medium Access control

CVE-2023-24880 — Microsoft Windows SmartScreen Security Feature Bypass Vulnerability

Windows SmartScreen Security Feature Bypass Vulnerability

Published Mar 14, 2023 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Used in ransomware campaigns (CISA)+10
  • EPSS 78% (30-day exploitation probability)+15
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Mar 14, 2023
EPSS FIRST
78.01%
ahead of 100% of scored CVEs · Oct 14, 2026
Affects
Microsoft
Windows 10 1607 and 18 more
CVSS base
4.4
Medium · 4 source(s)
Prioritization reference: 5.4 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: Apr 4, 2023 — passed 1290 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 20h2…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. Apply the fixed version or the patch documented under Remediation.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Windows 10 1607 < 10.0.14393.5786 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 1809 < 10.0.17763.4131 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 20h2 < 10.0.19042.2728 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 21h2 < 10.0.19044.2728 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 22h2 < 10.0.19045.2728 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 Version 1607 ≥ 10.0.14393.0 and < 10.0.14393.5786 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 1809 ≥ 10.0.0 and < 10.0.17763.4131≥ 10.0.17763.0 and < 10.0.17763.4131 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 20H2 ≥ 10.0.0 and < 10.0.19042.2728 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 21H2 ≥ 10.0.19043.0 and < 10.0.19044.2728 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 10 Version 22H2 ≥ 10.0.19045.0 and < 10.0.19045.2728 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 21h2 < 10.0.22000.1696 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 22h2 < 10.0.22000.1413 Vulnerable NIST National Vulnerability Database
Microsoft Windows 11 version 21H2 ≥ 10.0.0 and < 10.0.22000.1696 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows 11 version 22H2 ≥ 10.0.22621.0 and < 10.0.22621.1413 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2016 < 10.0.14393.5786 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2016 ≥ 10.0.14393.0 and < 10.0.14393.5786 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2016 (Server Core installation) ≥ 10.0.14393.0 and < 10.0.14393.5786 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2019 < 10.0.17763.4131 Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2019 ≥ 10.0.17763.0 and < 10.0.17763.4131 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2019 (Server Core installation) ≥ 10.0.17763.0 and < 10.0.17763.4131 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2022 ≥ 10.0.20348.0 and < 10.0.20348.1607 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Windows Server 2022 < 10.0.20348.1602 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.4 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
4.4 CVSS 3.1 Medium 1.8 2.5 secure@microsoft.com via NIST National Vulnerability Database
4.4 CVSS 3.1 Medium 1.8 2.5 nvd@nist.gov via NIST National Vulnerability Database
4.4 CVSS 3.1 Medium — — microsoft via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L (score shown at the top: secure@microsoft.com)
Sources assign different scores within the same severity band. For prioritization we use 5.4 (GitHub, Inc. via GitHub Security Advisories) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-863 · Incorrect Authorization

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Mar 14, 2023
Federal deadline
Apr 4, 2023
passed 1290 day(s) ago
Ransomware use
Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 78.01%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Audit administrative actions and access to resources outside each user’s normal pattern.
  • Hunt retroactively in logs from before Mar 14, 2023 (KEV listing): exploitation may have started earlier.
endpoint telemetry (EDR)authentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · microsoft/windows 10 version 1809, microsoft/windows server 2019, microsoft/windows server 2019 (server core installatio
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/windows 10 1607, microsoft/windows 10 1809, microsoft/windows 10 20h2, microsoft/windows 10 21h2, microsoft/wi
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 4.4
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2023
  • CVE published
    Mar 14, 2023 · microsoft
  • Added to CISA KEV catalog
    Mar 13, 2023 · CISA

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
2023-03
what else CISA listed that month
Access control
same class
CWE-863
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97841 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2023-24880 is "Microsoft Windows SmartScreen Security Feature Bypass Vulnerability", rated Medium. It affects Windows 10 1607 (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 4.4 describes technical severity. EPSS 78.01% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.