CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in microsoft. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2023-21726 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-21726?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-21726?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-21726 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Microsoft Windows 10 Version 1809 | from 10.0.17763.0 before 10.0.17763.3887 |
| Microsoft Windows 10 Version 1809 | from 10.0.0 before 10.0.17763.3887 |
| Microsoft Windows Server 2019 | from 10.0.17763.0 before 10.0.17763.3887 |
| Microsoft Windows Server 2019 (Server Core installation) | from 10.0.17763.0 before 10.0.17763.3887 |
| Microsoft Windows Server 2022 | from 10.0.20348.0 before 10.0.20348.1487 |
| Microsoft Windows 10 Version 20H2 | from 10.0.0 before 10.0.19042.2486 |
| Microsoft Windows 11 version 21H2 | from 10.0.0 before 10.0.22000.1455 |
| Microsoft Windows 10 Version 21H2 | from 10.0.19043.0 before 10.0.19044.2486 |
| Microsoft Windows 11 version 22H2 | from 10.0.22621.0 before 10.0.22621.1105 |
| Microsoft Windows 10 Version 22H2 | from 10.0.19045.0 before 10.0.19045.2486 |
| Microsoft Windows 10 Version 1507 | from 10.0.10240.0 before 10.0.10240.19685 |
| Microsoft Windows 10 Version 1607 | from 10.0.14393.0 before 10.0.14393.5648 |
| Microsoft Windows Server 2016 | from 10.0.14393.0 before 10.0.14393.5648 |
| Microsoft Windows Server 2016 (Server Core installation) | from 10.0.14393.0 before 10.0.14393.5648 |
| Microsoft Windows 7 | from 6.1.0 before 6.1.7601.26321 |
| Microsoft Windows 7 Service Pack 1 | from 6.1.0 before 6.1.7601.26321 |
| Microsoft Windows 8.1 | from 6.3.0 before 6.3.9600.20778 |
| Microsoft Windows Server 2008 Service Pack 2 | from 6.0.6003.0 before 6.0.6003.21872 |
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) | from 6.0.6003.0 before 6.0.6003.21872 |
| Microsoft Windows Server 2008 Service Pack 2 | from 6.0.6003.0 before 6.0.6003.21872 |
| Microsoft Windows Server 2008 R2 Service Pack 1 | from 6.1.7601.0 before 6.1.7601.26321 |
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) | from 6.1.7601.0 before 6.1.7601.26321 |
| Microsoft Windows Server 2012 | from 6.2.9200.0 before 6.2.9200.24075 |
| Microsoft Windows Server 2012 (Server Core installation) | from 6.2.9200.0 before 6.2.9200.24075 |
| Microsoft Windows Server 2012 R2 | from 6.3.9600.0 before 6.3.9600.20778 |
| Microsoft Windows Server 2012 R2 (Server Core installation) | from 6.3.9600.0 before 6.3.9600.20778 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.