CVE-2026-57432

HIGHNVD 8.48.4
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-07-13. NVD baseline CVSS 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: 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.43.10 have an integer overflow in S_measure_struct leading to an out-of-bounds heap read in pack and unpack.

S_measure_struct adds each item's size times its repeat count to a running total with no overflow check, so a large repeat count in a pack or unpack template wraps the signed SSize_t total negative. The @, X, and x position codes then guard their moves with a signed length comparison that passes when the length is negative, advancing the buffer pointer out of bounds.

A template derived from untrusted input can read heap memory past the buffer and return it to the caller.

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

Published

July 13, 2026

Last Modified

July 14, 2026

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 44× 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 15:37 UTCEPSS rescore
  2. 2026-07-28 12:20 UTCVendor advisory
  3. 2026-07-28 12:20 UTCGHSA enrichment
  4. 2026-07-28 00:26 UTCEG score recompute
  5. 2026-07-28 00:26 UTCVendor advisory
  6. 2026-07-28 00:26 UTCGHSA enrichment
  7. 2026-07-27 14:14 UTCEPSS rescore
  8. 2026-07-27 11:43 UTCGHSA enrichment
  9. 2026-07-26 23:48 UTCEG score recompute
  10. 2026-07-26 23:48 UTCVendor advisory
  11. 2026-07-26 23:48 UTCGHSA enrichment
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 14:54 UTCEPSS rescore
  14. 2026-07-26 11:53 UTCEG score recompute
  15. 2026-07-26 11:53 UTCVendor advisory
  16. 2026-07-26 11:53 UTCGHSA enrichment
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-25 14:18 UTCEPSS rescore
  19. 2026-07-24 14:18 UTCEPSS rescore
  20. 2026-07-24 14:18 UTCEPSS rescore
  21. 2026-07-23 14:18 UTCEPSS rescore
  22. 2026-07-23 14:18 UTCEPSS rescore
  23. 2026-07-23 03:20 UTCEG score recompute
  24. 2026-07-22 14:08 UTCEPSS rescore
  25. 2026-07-21 15:25 UTCEPSS rescore
Show 19 more
  1. 2026-07-20 17:08 UTCEPSS rescore
  2. 2026-07-19 14:31 UTCEPSS rescore
  3. 2026-07-19 14:31 UTCEPSS rescore
  4. 2026-07-19 02:29 UTCEPSS rescore
  5. 2026-07-18 10:04 UTCEPSS rescore
  6. 2026-07-16 18:53 UTCEG score recompute 8.40
  7. 2026-07-16 18:53 UTCVendor advisory
  8. 2026-07-16 18:53 UTCGHSA enrichment
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 02:00 UTCEPSS rescore
  14. 2026-07-14 13:45 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  15. 2026-07-13 20:25 UTCNVD update
  16. 2026-07-13 20:07 UTCMITRE cvelistV5
  17. 2026-07-13 18:08 UTCNVD update
  18. 2026-07-13 16:23 UTCEG score recompute
  19. 2026-07-13 16:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-57432?
CVE-2026-57432 is a high vulnerability published on July 13, 2026. Perl versions through 5.43.10 have an integer overflow in Smeasurestruct leading to an out-of-bounds heap read in pack and unpack. Smeasurestruct adds each item's size times its repeat count to a running total with no overflow check, so a large repeat count in a pack or unpack template wraps the…
When was CVE-2026-57432 disclosed?
CVE-2026-57432 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57432 actively exploited?
CVE-2026-57432 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 91.1% of all scored CVEs.
What is the CVSS score of CVE-2026-57432?
CVE-2026-57432 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-57432?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57432, 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-57432

Explore →

Is Your Infrastructure Affected by CVE-2026-57432?

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