CVE-2026-26113

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-03-10. The CNA's CVSS baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Untrusted pointer dereference in Microsoft Office allows an unauthorized attacker to execute code locally.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

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 computed (value × EchelonGraph’s weight)
Severity84% × 45%
The EG Score, 8.4 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 10, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-26113

Vendor Advisories for CVE-2026-26113(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 24× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 164 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 66 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-10-12 16:18 UTCEG score recompute
  3. 2026-10-11 20:00 UTCEG score recompute
  4. 2026-10-11 17:14 UTCEG score recompute
  5. 2026-10-11 14:45 UTCEG score recompute
  6. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  10. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 73 more
  1. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-08-16 12:07 UTCEG score recompute
  24. 2026-08-16 12:07 UTCVendor advisory
  25. 2026-08-16 12:07 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  26. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-08-14 20:38 UTCVendor advisory
  29. 2026-08-14 20:38 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  30. 2026-08-14 08:04 UTCEG score recompute
  31. 2026-08-14 08:04 UTCVendor advisory
  32. 2026-08-14 08:04 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  33. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  34. 2026-08-12 23:28 UTCEG score recompute
  35. 2026-08-12 23:28 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  36. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  37. 2026-08-11 22:00 UTCEG score recompute
  38. 2026-08-11 22:00 UTCVendor advisory
  39. 2026-08-11 22:00 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  40. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  41. 2026-08-11 05:08 UTCEG score recompute
  42. 2026-08-11 05:08 UTCVendor advisory
  43. 2026-08-11 05:08 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  44. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  45. 2026-08-10 08:27 UTCVendor advisory
  46. 2026-08-10 08:27 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  47. 2026-08-09 20:05 UTCEG score recompute
  48. 2026-08-09 20:05 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  49. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  50. 2026-08-09 07:44 UTCEG score recompute
  51. 2026-08-09 07:44 UTCVendor advisory
  52. 2026-08-09 07:44 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  53. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  54. 2026-08-08 07:27 UTCVendor advisory
  55. 2026-08-08 07:27 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  56. 2026-08-07 19:05 UTCEG score recompute
  57. 2026-08-07 19:05 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  58. 2026-08-06 20:06 UTCEG score recompute
  59. 2026-08-06 20:06 UTCVendor advisory
  60. 2026-08-06 20:06 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  61. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  62. 2026-08-06 02:13 UTCEG score recompute
  63. 2026-08-06 02:13 UTCVendor advisory
  64. 2026-08-06 02:13 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  65. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  66. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  67. 2026-08-04 01:38 UTCEG score recompute
  68. 2026-08-04 01:38 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  69. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  70. 2026-08-02 17:57 UTCEG score recompute
  71. 2026-08-02 17:57 UTCVendor advisory
  72. 2026-08-02 17:57 UTCGHSA enrichmentGHSA-55wj-q5rx-5h35 · GitHub severity HIGH · GitHub CVSS 8.4
  73. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile

Frequently asked(5)

What is CVE-2026-26113?
CVE-2026-26113 is a high-severity vulnerability; its CVE record was published on March 10, 2026. Untrusted pointer dereference in Microsoft Office allows an unauthorized attacker to execute code locally.
When was CVE-2026-26113 made public?
CVE-2026-26113 was made public on March 10, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on March 10, 2026. EchelonGraph's copy of the record carries a last-modified date of June 19, 2026; the record at its source may have been updated since.
Is CVE-2026-26113 actively exploited?
CVE-2026-26113 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-26113?
CVE-2026-26113 has a CVSS base score of 8.4 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-26113?
A fix for CVE-2026-26113 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-26113 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-26113

Explore →

Is Your Infrastructure Affected by CVE-2026-26113?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.