CVE-2026-50380

CRITICALPre-NVD 9.69.6
EchelonGraph scoreHIGH confidence

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

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

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

Heap-based buffer overflow in Windows GDI+ allows an unauthorized attacker to execute code over a network.

CVSS v3
9.6
EG Score
9.6(high)
EG Risk
43(Track)
EG Risk 43/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
Severity96% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 26, 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-50380

Vendor Advisories for CVE-2026-50380(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 21× in last 7d / 62× 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-26 21:38 UTCVendor advisory
  2. 2026-07-26 21:38 UTCGHSA enrichment
  3. 2026-07-26 17:23 UTCVendor advisory
  4. 2026-07-26 17:23 UTCGHSA enrichment
  5. 2026-07-26 15:59 UTCEG score recompute
  6. 2026-07-26 15:59 UTCVendor advisory
  7. 2026-07-26 15:59 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 11:45 UTCEG score recompute
  10. 2026-07-26 11:45 UTCVendor advisory
  11. 2026-07-26 11:44 UTCGHSA enrichment
  12. 2026-07-26 04:56 UTCEG score recompute
  13. 2026-07-26 04:56 UTCVendor advisory
  14. 2026-07-26 04:56 UTCGHSA enrichment
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-24 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 03:18 UTCEG score recompute
  19. 2026-07-22 14:08 UTCEPSS rescore
  20. 2026-07-21 15:25 UTCEPSS rescore
  21. 2026-07-20 17:08 UTCEPSS rescore
  22. 2026-07-19 14:31 UTCEPSS rescore
  23. 2026-07-19 14:31 UTCEPSS rescore
  24. 2026-07-19 03:20 UTCEG score recompute
  25. 2026-07-19 03:20 UTCVendor advisory
Show 37 more
  1. 2026-07-19 03:20 UTCGHSA enrichment
  2. 2026-07-19 02:29 UTCEPSS rescore
  3. 2026-07-18 10:04 UTCEPSS rescore
  4. 2026-07-17 05:40 UTCVendor advisory
  5. 2026-07-17 05:40 UTCGHSA enrichment
  6. 2026-07-17 01:25 UTCVendor advisory
  7. 2026-07-17 01:24 UTCGHSA enrichment
  8. 2026-07-16 21:10 UTCVendor advisory
  9. 2026-07-16 21:10 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 16:56 UTCVendor advisory
  12. 2026-07-16 16:56 UTCGHSA enrichment
  13. 2026-07-16 12:20 UTCVendor advisory
  14. 2026-07-16 12:19 UTCGHSA enrichment
  15. 2026-07-16 08:03 UTCVendor advisory
  16. 2026-07-16 08:02 UTCGHSA enrichment
  17. 2026-07-16 03:48 UTCVendor advisory
  18. 2026-07-16 03:48 UTCGHSA enrichment
  19. 2026-07-15 23:33 UTCVendor advisory
  20. 2026-07-15 23:33 UTCGHSA enrichment
  21. 2026-07-15 19:19 UTCVendor advisory
  22. 2026-07-15 19:19 UTCGHSA enrichment
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 15:05 UTCVendor advisory
  26. 2026-07-15 15:05 UTCGHSA enrichment
  27. 2026-07-15 10:51 UTCVendor advisory
  28. 2026-07-15 10:51 UTCGHSA enrichment
  29. 2026-07-15 06:35 UTCVendor advisory
  30. 2026-07-15 06:35 UTCGHSA enrichment
  31. 2026-07-15 02:21 UTCVendor advisory
  32. 2026-07-15 02:20 UTCGHSA enrichment
  33. 2026-07-14 22:06 UTCVendor advisory
  34. 2026-07-14 22:06 UTCGHSA enrichment
  35. 2026-07-14 17:50 UTCEG score recompute
  36. 2026-07-14 17:50 UTCVendor advisory
  37. 2026-07-14 17:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-50380?
CVE-2026-50380 is a critical vulnerability published on July 14, 2026. Heap-based buffer overflow in Windows GDI+ allows an unauthorized attacker to execute code over a network.
When was CVE-2026-50380 disclosed?
CVE-2026-50380 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50380 actively exploited?
CVE-2026-50380 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.7% of all scored CVEs.
What is the CVSS score of CVE-2026-50380?
CVE-2026-50380 has a CVSS v4.0 base score of 9.6 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50380?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50380, 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-50380

Explore →

Is Your Infrastructure Affected by CVE-2026-50380?

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