CVE-2026-50039

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-23. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
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.5Exploit: None knownExposed: 0

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

The affected product is vulnerable to a stack-based buffer overflow, which may allow an attacker to cause a memory corruption via a Read Request.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 23, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

MZ Automation libIEC61850 | CISA

MZ Automation libIEC61850 | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/news-events/ics-advisories/icsa-26-204-06

Vendor Advisories for CVE-2026-50039(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 14× in last 7d / 14× 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-27 22:56 UTCEG score recompute
  2. 2026-07-27 22:56 UTCGHSA enrichment
  3. 2026-07-27 11:59 UTCGHSA enrichment
  4. 2026-07-27 01:02 UTCEG score recompute
  5. 2026-07-27 01:02 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:05 UTCEG score recompute
  8. 2026-07-26 14:05 UTCGHSA enrichment
  9. 2026-07-26 03:07 UTCEG score recompute
  10. 2026-07-26 03:07 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-23 20:47 UTCEG score recompute
  14. 2026-07-23 20:46 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50039?
CVE-2026-50039 is a high vulnerability published on July 23, 2026. The affected product is vulnerable to a stack-based buffer overflow, which may allow an attacker to cause a memory corruption via a Read Request.
When was CVE-2026-50039 disclosed?
CVE-2026-50039 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50039 actively exploited?
CVE-2026-50039 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 81.4% of all scored CVEs.
What is the CVSS score of CVE-2026-50039?
CVE-2026-50039 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-50039?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50039, 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-50039

Explore →

Is Your Infrastructure Affected by CVE-2026-50039?

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

Start Free Scan →Browse All CVEs