CVE-2026-15534

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreHIGH confidence

Score 5.7 from GitHub Security Advisory published 2026-08-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.7; sources differ by 0.0.

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

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

Perl versions through 5.45.1 have out-of-bounds heap reads and writes during regular expression matching via an undersized superlinear cache in S_regmatch.

The regex engine's superlinear cache holds one bit per subject position for each participating WHILEM node, so the bit count is the subject length plus one times the number of nodes. Nothing checks that product for positive overflow of the signed 32-bit count: a 286331153 byte subject matched against a pattern with 15 participating nodes stores the count as 14, leaving a two byte cache. The cache is then indexed from the real match position and node number, so reads go past the end of the allocation, and on failure CACHEsayNO sets a bit past it.

A caller that matches an attacker controlled subject of this size against a pattern of this shape can crash the process or corrupt heap memory.

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

Published

August 9, 2026

Last Modified

August 12, 2026

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 39× 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-08-20 14:55 UTCEG score recompute
  2. 2026-08-20 14:55 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-19 15:21 UTCGHSA enrichment
  5. 2026-08-18 15:39 UTCEG score recompute
  6. 2026-08-18 15:39 UTCGHSA enrichment
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 16:00 UTCEG score recompute
  9. 2026-08-17 16:00 UTCGHSA enrichment
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 16:28 UTCEG score recompute
  12. 2026-08-16 16:28 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 16:57 UTCEG score recompute
  16. 2026-08-15 16:57 UTCGHSA enrichment
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 17:24 UTCEG score recompute
  19. 2026-08-14 17:24 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 17:52 UTCEG score recompute
  22. 2026-08-13 17:52 UTCGHSA enrichment
  23. 2026-08-12 18:19 UTCGHSA enrichment
  24. 2026-08-12 17:51 UTCEG score recompute 5.70
  25. 2026-08-12 17:51 UTCGHSA enrichment
Show 14 more
  1. 2026-08-12 17:50 UTCMITRE cvelistV5CVSS v3 → 5.7 · severity → MEDIUM
  2. 2026-08-12 13:50 UTCEPSS rescore
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-09 22:17 UTCNVD update
  6. 2026-08-09 22:16 UTCGHSA enrichment
  7. 2026-08-09 22:16 UTCMITRE cvelistV5
  8. 2026-08-09 21:20 UTCGHSA enrichment
  9. 2026-08-09 21:19 UTCNVD update
  10. 2026-08-09 20:21 UTCGHSA enrichment
  11. 2026-08-09 20:21 UTCMITRE cvelistV5
  12. 2026-08-09 18:19 UTCNVD update
  13. 2026-08-09 18:01 UTCEG score recompute
  14. 2026-08-09 18:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15534?
CVE-2026-15534 is a medium vulnerability published on August 9, 2026. Perl versions through 5.45.1 have out-of-bounds heap reads and writes during regular expression matching via an undersized superlinear cache in S_regmatch. The regex engine's superlinear cache holds one bit per subject position for each participating WHILEM node, so the bit count is the subject…
When was CVE-2026-15534 disclosed?
CVE-2026-15534 was first published in the National Vulnerability Database on August 9, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15534 actively exploited?
CVE-2026-15534 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 94.2% of all scored CVEs.
What is the CVSS score of CVE-2026-15534?
CVE-2026-15534 has a CVSS v3.1 base score of 5.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-15534?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15534, 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-15534

Explore →

Is Your Infrastructure Affected by CVE-2026-15534?

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