CVE-2026-55022

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

Access of resource using incompatible type ('type confusion') in Microsoft Office allows an unauthorized attacker to execute code locally.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 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 27, 2026

Advisory Details (1)

Auto-updated Jul 14, 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-55022

Vendor Advisories for CVE-2026-55022(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 24× in last 7d / 46× 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 00:05 UTCVendor advisory
  2. 2026-07-28 00:05 UTCGHSA enrichment
  3. 2026-07-27 22:23 UTCVendor advisory
  4. 2026-07-27 22:23 UTCGHSA enrichment
  5. 2026-07-27 16:23 UTCEG score recompute
  6. 2026-07-27 16:23 UTCVendor advisory
  7. 2026-07-27 16:23 UTCGHSA enrichment
  8. 2026-07-27 05:53 UTCVendor advisory
  9. 2026-07-27 05:53 UTCGHSA enrichment
  10. 2026-07-26 17:53 UTCVendor advisory
  11. 2026-07-26 17:53 UTCGHSA enrichment
  12. 2026-07-26 16:50 UTCEG score recompute
  13. 2026-07-26 16:50 UTCVendor advisory
  14. 2026-07-26 16:50 UTCGHSA enrichment
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-26 04:51 UTCEG score recompute
  17. 2026-07-26 04:51 UTCVendor advisory
  18. 2026-07-26 04:50 UTCGHSA enrichment
  19. 2026-07-25 14:18 UTCEPSS rescore
  20. 2026-07-24 14:18 UTCEPSS rescore
  21. 2026-07-23 14:18 UTCEPSS rescore
  22. 2026-07-23 03:20 UTCEG score recompute
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-21 15:25 UTCEPSS rescore
  25. 2026-07-20 17:08 UTCEPSS rescore
Show 21 more
  1. 2026-07-19 02:55 UTCEG score recompute
  2. 2026-07-19 02:55 UTCVendor advisory
  3. 2026-07-19 02:55 UTCGHSA enrichment
  4. 2026-07-19 02:29 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-17 05:42 UTCVendor advisory
  7. 2026-07-17 05:42 UTCGHSA enrichment
  8. 2026-07-16 17:43 UTCVendor advisory
  9. 2026-07-16 17:43 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 05:44 UTCVendor advisory
  12. 2026-07-16 05:44 UTCGHSA enrichment
  13. 2026-07-15 17:45 UTCVendor advisory
  14. 2026-07-15 17:45 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 05:45 UTCVendor advisory
  18. 2026-07-15 05:45 UTCGHSA enrichment
  19. 2026-07-14 17:44 UTCEG score recompute
  20. 2026-07-14 17:44 UTCVendor advisory
  21. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-55022?
CVE-2026-55022 is a high vulnerability published on July 14, 2026. Access of resource using incompatible type ('type confusion') in Microsoft Office allows an unauthorized attacker to execute code locally.
When was CVE-2026-55022 disclosed?
CVE-2026-55022 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55022 actively exploited?
CVE-2026-55022 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 69.7% of all scored CVEs.
What is the CVSS score of CVE-2026-55022?
CVE-2026-55022 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-55022?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55022, 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-55022

Explore →

Is Your Infrastructure Affected by CVE-2026-55022?

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

Start Free Scan →Browse All CVEs