Reliance on untrusted inputs in a security decision in Microsoft Office Word allows an unauthorized attacker to bypass a security feature locally.
CVE-2026-21514
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-02-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 2%
- EPSS %ILE
- 74%
- KEV
- ⚠ Exploited
Published
February 10, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Jun 3, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-21514Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21514Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 95× in last 7d / 399× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 1,423 total refreshes for this CVE.
- 2026-09-19 21:03 UTCVendor advisory
- 2026-09-19 21:03 UTCGHSA enrichment
- 2026-09-19 16:51 UTCEG score recompute
- 2026-09-19 16:51 UTCVendor advisory
- 2026-09-19 16:51 UTCGHSA enrichment
- 2026-09-19 12:39 UTCVendor advisory
- 2026-09-19 12:39 UTCGHSA enrichment
- 2026-09-19 08:26 UTCVendor advisory
- 2026-09-19 08:26 UTCGHSA enrichment
- 2026-09-19 04:14 UTCVendor advisory
- 2026-09-19 04:14 UTCGHSA enrichment
- 2026-09-19 00:03 UTCVendor advisory
- 2026-09-19 00:03 UTCGHSA enrichment
- 2026-09-18 19:51 UTCEG score recompute
- 2026-09-18 19:51 UTCVendor advisory
- 2026-09-18 19:51 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 15:40 UTCVendor advisory
- 2026-09-18 15:39 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 11:25 UTCVendor advisory
- 2026-09-18 11:25 UTCGHSA enrichment
- 2026-09-18 07:13 UTCVendor advisory
- 2026-09-18 07:13 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-18 03:02 UTCVendor advisory
- 2026-09-18 03:02 UTCGHSA enrichment
- 2026-09-17 22:50 UTCEG score recompute
- 2026-09-17 22:50 UTCVendor advisory
- 2026-09-17 22:49 UTCGHSA enrichment
- 2026-09-17 18:35 UTCVendor advisory
- 2026-09-17 18:35 UTCGHSA enrichment
- 2026-09-17 14:22 UTCVendor advisory
- 2026-09-17 14:22 UTCGHSA enrichment
- 2026-09-17 10:10 UTCVendor advisory
- 2026-09-17 10:10 UTCGHSA enrichment
- 2026-09-17 05:58 UTCVendor advisory
- 2026-09-17 05:57 UTCGHSA enrichment
- 2026-09-17 01:44 UTCVendor advisory
- 2026-09-17 01:44 UTCGHSA enrichment
- 2026-09-16 21:32 UTCVendor advisory
- 2026-09-16 21:32 UTCGHSA enrichment
- 2026-09-16 17:20 UTCEG score recompute
- 2026-09-16 17:20 UTCVendor advisory
- 2026-09-16 17:19 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 13:06 UTCVendor advisory
- 2026-09-16 13:06 UTCGHSA enrichment
- 2026-09-16 08:54 UTCEG score recompute
- 2026-09-16 08:54 UTCVendor advisory
- 2026-09-16 08:54 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 04:42 UTCVendor advisory
- 2026-09-16 04:42 UTCGHSA enrichment
- 2026-09-16 00:31 UTCVendor advisory
- 2026-09-16 00:30 UTCGHSA enrichment
- 2026-09-15 20:16 UTCVendor advisory
- 2026-09-15 20:16 UTCGHSA enrichment
- 2026-09-15 16:04 UTCVendor advisory
- 2026-09-15 16:04 UTCGHSA enrichment
- 2026-09-15 11:52 UTCVendor advisory
- 2026-09-15 11:52 UTCGHSA enrichment
- 2026-09-15 07:40 UTCVendor advisory
- 2026-09-15 07:40 UTCGHSA enrichment
- 2026-09-15 03:28 UTCEG score recompute
- 2026-09-15 03:28 UTCVendor advisory
- 2026-09-15 03:28 UTCGHSA enrichment
- 2026-09-14 23:16 UTCVendor advisory
- 2026-09-14 23:16 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 19:04 UTCVendor advisory
- 2026-09-14 19:04 UTCGHSA enrichment
- 2026-09-14 14:52 UTCVendor advisory
- 2026-09-14 14:52 UTCGHSA enrichment
- 2026-09-14 10:40 UTCVendor advisory
- 2026-09-14 10:40 UTCGHSA enrichment
- 2026-09-14 06:28 UTCVendor advisory
- 2026-09-14 06:28 UTCGHSA enrichment
- 2026-09-14 02:16 UTCVendor advisory
- 2026-09-14 02:16 UTCGHSA enrichment
- 2026-09-13 22:05 UTCVendor advisory
- 2026-09-13 22:05 UTCGHSA enrichment
- 2026-09-13 17:53 UTCEG score recompute
- 2026-09-13 17:53 UTCVendor advisory
- 2026-09-13 17:53 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 13:41 UTCVendor advisory
- 2026-09-13 13:41 UTCGHSA enrichment
- 2026-09-13 09:30 UTCVendor advisory
- 2026-09-13 09:30 UTCGHSA enrichment
- 2026-09-13 05:18 UTCVendor advisory
- 2026-09-13 05:18 UTCGHSA enrichment
- 2026-09-13 01:07 UTCVendor advisory
- 2026-09-13 01:07 UTCGHSA enrichment
- 2026-09-12 20:55 UTCVendor advisory
- 2026-09-12 20:55 UTCGHSA enrichment
- 2026-09-12 16:43 UTCEG score recompute
- 2026-09-12 16:43 UTCVendor advisory
- 2026-09-12 16:43 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCChaitanyaHaritash/CVE-2026-21514_CVE-2026-21510First seen May 4, 2026
CVE-2026-21514 & CVE-2026-21510 (Because MS-Office Fascinates me)
Open source ↗
Frequently asked(6)
What is CVE-2026-21514?
When was CVE-2026-21514 disclosed?
Is CVE-2026-21514 actively exploited?
What is the CVSS score of CVE-2026-21514?
Which products are affected by CVE-2026-21514?
How do I remediate CVE-2026-21514?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-21514
Is Your Infrastructure Affected by CVE-2026-21514?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.