CVE-2026-59144

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-21. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
9.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: 9.8Exploit: None knownExposed: 0

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

Data::RingBuffer::Shared versions before 0.04 for Perl allow a stack buffer overflow via an unvalidated elem_size in ring_read_seq.

The attach-time validator ring_validate_header checks the capacity-overflow and total_size consistency of the header but never caps elem_size against the destination size. ring_read_seq does memcpy(out, ring_slot(h, seq), elem_size) with elem_size read raw from the mmap'd segment, copying into a fixed 8-byte destination scalar. An elem_size larger than 8 bytes writes past the destination.

A local peer that can write the backing file can leave the header valid while setting a large elem_size, so the next read copies a file-controlled length into the fixed 8-byte stack buffer, corrupting adjacent stack frames.

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

Published

July 21, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-59144(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 36× in last 7d / 36× 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 07:33 UTCGHSA enrichment
  2. 2026-07-28 03:30 UTCGHSA enrichment
  3. 2026-07-27 23:29 UTCGHSA enrichment
  4. 2026-07-27 19:15 UTCGHSA enrichment
  5. 2026-07-27 15:13 UTCEG score recompute
  6. 2026-07-27 15:13 UTCGHSA enrichment
  7. 2026-07-27 14:14 UTCEPSS rescore
  8. 2026-07-27 10:38 UTCGHSA enrichment
  9. 2026-07-27 06:34 UTCGHSA enrichment
  10. 2026-07-27 02:31 UTCGHSA enrichment
  11. 2026-07-26 22:25 UTCGHSA enrichment
  12. 2026-07-26 18:24 UTCEG score recompute
  13. 2026-07-26 18:24 UTCGHSA enrichment
  14. 2026-07-26 14:54 UTCEPSS rescore
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-26 14:14 UTCEG score recompute
  17. 2026-07-26 14:14 UTCGHSA enrichment
  18. 2026-07-26 10:04 UTCEG score recompute
  19. 2026-07-26 10:04 UTCGHSA enrichment
  20. 2026-07-25 14:18 UTCEPSS rescore
  21. 2026-07-25 14:18 UTCEPSS rescore
  22. 2026-07-24 14:18 UTCEPSS rescore
  23. 2026-07-24 14:18 UTCEPSS rescore
  24. 2026-07-23 14:18 UTCEPSS rescore
  25. 2026-07-23 14:18 UTCEPSS rescore
Show 11 more
  1. 2026-07-23 03:21 UTCEG score recompute
  2. 2026-07-22 23:02 UTCEG score recompute
  3. 2026-07-22 23:02 UTCGHSA enrichment
  4. 2026-07-22 20:05 UTCEG score recompute 9.80
  5. 2026-07-22 20:05 UTCGHSA enrichment
  6. 2026-07-22 20:00 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-22 14:08 UTCEPSS rescore
  9. 2026-07-21 21:19 UTCNVD update
  10. 2026-07-21 19:45 UTCEG score recompute
  11. 2026-07-21 19:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59144?
CVE-2026-59144 is a critical vulnerability published on July 21, 2026. Data::RingBuffer::Shared versions before 0.04 for Perl allow a stack buffer overflow via an unvalidated elemsize in ringread_seq. The attach-time validator ringvalidateheader checks the capacity-overflow and totalsize consistency of the header but never caps elemsize against the destination size.…
When was CVE-2026-59144 disclosed?
CVE-2026-59144 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59144 actively exploited?
CVE-2026-59144 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 62.6% of all scored CVEs.
What is the CVSS score of CVE-2026-59144?
CVE-2026-59144 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-59144?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59144, 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-59144

Explore →

Is Your Infrastructure Affected by CVE-2026-59144?

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