CVE-2026-55026

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreHIGH confidence

Score 6.2 from GitHub Security Advisory published 2026-07-14. the CNA's CVSS baseline 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Integer overflow or wraparound in Microsoft Office allows an unauthorized attacker to disclose information locally.

CVSS v3
6.2
EG Score
6.2(high)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

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
Severity62% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 28, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security 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-55026

Vendor Advisories for CVE-2026-55026(2)

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 25× in last 7d / 49× 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.

  1. 2026-07-28 21:42 UTCVendor advisory
  2. 2026-07-28 21:41 UTCGHSA enrichment
  3. 2026-07-28 15:56 UTCEG score recompute
  4. 2026-07-28 15:56 UTCVendor advisory
  5. 2026-07-28 15:55 UTCGHSA enrichment
  6. 2026-07-28 15:37 UTCEPSS rescore
  7. 2026-07-28 00:05 UTCVendor advisory
  8. 2026-07-28 00:05 UTCGHSA enrichment
  9. 2026-07-27 22:23 UTCVendor advisory
  10. 2026-07-27 22:22 UTCGHSA enrichment
  11. 2026-07-27 16:23 UTCEG score recompute
  12. 2026-07-27 16:23 UTCVendor advisory
  13. 2026-07-27 16:23 UTCGHSA enrichment
  14. 2026-07-26 17:53 UTCEG score recompute
  15. 2026-07-26 17:53 UTCVendor advisory
  16. 2026-07-26 17:53 UTCGHSA enrichment
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 04:50 UTCEG score recompute
  19. 2026-07-26 04:50 UTCVendor advisory
  20. 2026-07-26 04:50 UTCGHSA enrichment
  21. 2026-07-25 14:18 UTCEPSS rescore
  22. 2026-07-24 14:18 UTCEPSS rescore
  23. 2026-07-23 14:18 UTCEPSS rescore
  24. 2026-07-23 03:20 UTCEG score recompute
  25. 2026-07-22 14:08 UTCEPSS rescore
Show 24 more
  1. 2026-07-21 15:25 UTCEPSS rescore
  2. 2026-07-20 17:08 UTCEPSS rescore
  3. 2026-07-19 14:31 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:55 UTCEG score recompute
  6. 2026-07-19 02:55 UTCVendor advisory
  7. 2026-07-19 02:55 UTCGHSA enrichment
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-17 07:42 UTCEG score recompute
  11. 2026-07-17 07:42 UTCVendor advisory
  12. 2026-07-17 07:42 UTCGHSA enrichment
  13. 2026-07-16 22:05 UTCMITRE cvelistV5CVSS v3 → 6.2
  14. 2026-07-16 20:34 UTCVendor advisory
  15. 2026-07-16 20:34 UTCGHSA enrichment
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-16 16:30 UTCNVD updateCVSS v3 → 5.5
  18. 2026-07-15 19:09 UTCVendor advisory
  19. 2026-07-15 19:09 UTCGHSA enrichment
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-14 17:44 UTCEG score recompute
  23. 2026-07-14 17:44 UTCVendor advisory
  24. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-55026?
CVE-2026-55026 is a medium vulnerability published on July 14, 2026. Integer overflow or wraparound in Microsoft Office allows an unauthorized attacker to disclose information locally.
When was CVE-2026-55026 disclosed?
CVE-2026-55026 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55026 actively exploited?
CVE-2026-55026 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.0% of all scored CVEs.
What is the CVSS score of CVE-2026-55026?
CVE-2026-55026 has a CVSS v4.0 base score of 6.2 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-55026?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55026, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55026?

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

Start Free Scan →Browse All CVEs