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
- 71.9%
- KEV
- ⚠ Exploited
Published
February 10, 2026
Last Modified
February 11, 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 93× in last 7d / 392× 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 687 total refreshes for this CVE.
- 2026-07-23 03:06 UTCEG score recompute
- 2026-07-22 20:18 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 16:06 UTCEG score recompute
- 2026-07-22 16:06 UTCVendor advisory
- 2026-07-22 16:05 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 11:52 UTCVendor advisory
- 2026-07-22 11:52 UTCGHSA enrichment
- 2026-07-22 07:40 UTCVendor advisory
- 2026-07-22 07:40 UTCGHSA enrichment
- 2026-07-22 03:28 UTCVendor advisory
- 2026-07-22 03:27 UTCGHSA enrichment
- 2026-07-21 23:15 UTCVendor advisory
- 2026-07-21 23:15 UTCGHSA enrichment
- 2026-07-21 18:45 UTCEG score recompute
- 2026-07-21 18:45 UTCVendor advisory
- 2026-07-21 18:45 UTCGHSA enrichment
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 14:33 UTCVendor advisory
- 2026-07-21 14:33 UTCGHSA enrichment
- 2026-07-21 10:20 UTCVendor advisory
- 2026-07-21 10:20 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-21 06:08 UTCVendor advisory
- 2026-07-21 06:08 UTCGHSA enrichment
- 2026-07-21 01:57 UTCVendor advisory
- 2026-07-21 01:57 UTCGHSA enrichment
- 2026-07-20 21:45 UTCVendor advisory
- 2026-07-20 21:45 UTCGHSA enrichment
- 2026-07-20 17:33 UTCEG score recompute
- 2026-07-20 17:33 UTCVendor advisory
- 2026-07-20 17:33 UTCGHSA enrichment
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 13:21 UTCGHSA enrichment
- 2026-07-20 09:09 UTCVendor advisory
- 2026-07-20 09:09 UTCGHSA enrichment
- 2026-07-20 04:58 UTCVendor advisory
- 2026-07-20 04:58 UTCGHSA enrichment
- 2026-07-20 00:46 UTCVendor advisory
- 2026-07-19 20:34 UTCVendor advisory
- 2026-07-19 20:34 UTCGHSA enrichment
- 2026-07-19 16:22 UTCEG score recompute
- 2026-07-19 16:22 UTCVendor advisory
- 2026-07-19 16:22 UTCGHSA enrichment
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 12:10 UTCVendor advisory
- 2026-07-19 12:10 UTCGHSA enrichment
- 2026-07-19 07:58 UTCVendor advisory
- 2026-07-19 07:58 UTCGHSA enrichment
- 2026-07-19 03:46 UTCEG score recompute
- 2026-07-19 03:46 UTCVendor advisory
- 2026-07-19 03:46 UTCGHSA enrichment
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 23:34 UTCGHSA enrichment
- 2026-07-18 19:23 UTCVendor advisory
- 2026-07-18 19:23 UTCGHSA enrichment
- 2026-07-18 15:12 UTCVendor advisory
- 2026-07-18 15:11 UTCGHSA enrichment
- 2026-07-18 10:59 UTCEG score recompute
- 2026-07-18 10:59 UTCVendor advisory
- 2026-07-18 10:59 UTCGHSA enrichment
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 06:47 UTCVendor advisory
- 2026-07-18 06:47 UTCGHSA enrichment
- 2026-07-18 02:35 UTCVendor advisory
- 2026-07-18 02:35 UTCGHSA enrichment
- 2026-07-17 22:23 UTCVendor advisory
- 2026-07-17 22:23 UTCGHSA enrichment
- 2026-07-17 18:11 UTCVendor advisory
- 2026-07-17 18:11 UTCGHSA enrichment
- 2026-07-17 13:59 UTCVendor advisory
- 2026-07-17 13:59 UTCGHSA enrichment
- 2026-07-17 09:47 UTCEG score recompute
- 2026-07-17 09:47 UTCVendor advisory
- 2026-07-17 09:47 UTCGHSA enrichment
- 2026-07-17 05:35 UTCVendor advisory
- 2026-07-17 05:35 UTCGHSA enrichment
- 2026-07-17 01:23 UTCVendor advisory
- 2026-07-17 01:22 UTCGHSA enrichment
- 2026-07-16 21:11 UTCVendor advisory
- 2026-07-16 21:11 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 16:59 UTCVendor advisory
- 2026-07-16 16:59 UTCGHSA enrichment
- 2026-07-16 12:47 UTCGHSA enrichment
- 2026-07-16 08:35 UTCGHSA enrichment
- 2026-07-16 04:24 UTCVendor advisory
- 2026-07-16 04:24 UTCGHSA enrichment
- 2026-07-16 00:12 UTCVendor advisory
- 2026-07-16 00:12 UTCGHSA enrichment
- 2026-07-15 20:01 UTCVendor advisory
- 2026-07-15 20:01 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
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.