CVE-2026-9538

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-26. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

A fix is available — apply it.

Archive::Tar versions before 3.10 for Perl allow memory exhaustion via attacker controlled entry size field in tar header.

_read_tar() reads each entry's payload with $handle->read($$data, $block), where $block is derived from the entry's 12-byte size field in the tar header with no upper bound on that value.

A crafted header declaring a multi-gigabyte size causes Perl to allocate a scalar of that size.

CVSS v3
7.5
EG Score
7.5(medium)
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
38%
KEV
Not listed

Published

May 26, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-9538: Archive::Tar versions before 3.10 for Perl allow memory exhaustion via attacker controlled entry size field in tar header

http://www.openwall.com/lists/oss-security/2026/05/26/4

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatperl-Archive-Tar-0:3.02-512.el10_2.22026-08-03redhat
redhatperl-Archive-Tar-0:2.30-3.el8_102026-08-03redhat
redhatperl-Archive-Tar-0:2.38-6.el9_8.22026-08-03redhat
redhatperl:5.32-8100020260723094404.651ee29f2026-07-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
perl5.32.1-4 ... 5.44.0-1 (59 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
perl5.36.0-10 ... 5.44.0-1 (43 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
perl5.40.1-6 ... 5.44.0-1 (11 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
perl5.40.1-6 ... 5.42.2-3 (9 versions)5.42.3-1

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 37× 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.

Showing the most recent 100 of 240 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:32 UTCEPSS rescore
  3. 2026-09-16 14:09 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-15 03:12 UTCEPSS rescore
  6. 2026-09-13 16:48 UTCEPSS rescore
  7. 2026-09-12 15:02 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:38 UTCEPSS rescore
  10. 2026-09-11 03:23 UTCOSV refresh
  11. 2026-09-10 09:35 UTCEPSS rescore
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-06 13:48 UTCEPSS rescore
  14. 2026-09-05 15:31 UTCEPSS rescore
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-30 19:18 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:42 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:47 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 16:26 UTCEG score recompute
  2. 2026-08-23 16:26 UTCVendor advisory
  3. 2026-08-23 16:26 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 21:32 UTCEG score recompute
  7. 2026-08-21 21:32 UTCVendor advisory
  8. 2026-08-21 21:32 UTCGHSA enrichment
  9. 2026-08-20 22:56 UTCEPSS rescore
  10. 2026-08-20 18:21 UTCEG score recompute
  11. 2026-08-20 18:21 UTCVendor advisory
  12. 2026-08-20 18:21 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:49 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 09:36 UTCVendor advisory
  17. 2026-08-17 09:36 UTCGHSA enrichment
  18. 2026-08-16 16:34 UTCEG score recompute
  19. 2026-08-16 16:34 UTCVendor advisory
  20. 2026-08-16 16:34 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 03:09 UTCEG score recompute
  23. 2026-08-16 03:09 UTCVendor advisory
  24. 2026-08-16 03:09 UTCGHSA enrichment
  25. 2026-08-16 02:15 UTCEPSS rescore
  26. 2026-08-15 02:00 UTCEG score recompute
  27. 2026-08-15 02:00 UTCVendor advisory
  28. 2026-08-15 02:00 UTCGHSA enrichment
  29. 2026-08-15 01:31 UTCEPSS rescore
  30. 2026-08-14 13:53 UTCVendor advisory
  31. 2026-08-14 13:53 UTCGHSA enrichment
  32. 2026-08-14 01:46 UTCEG score recompute
  33. 2026-08-14 01:46 UTCVendor advisory
  34. 2026-08-14 01:46 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 02:17 UTCVendor advisory
  37. 2026-08-13 02:17 UTCGHSA enrichment
  38. 2026-08-12 14:10 UTCEG score recompute
  39. 2026-08-12 14:10 UTCVendor advisory
  40. 2026-08-12 14:10 UTCGHSA enrichment
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-12 01:50 UTCEG score recompute
  43. 2026-08-12 01:50 UTCVendor advisory
  44. 2026-08-12 01:50 UTCGHSA enrichment
  45. 2026-08-11 13:43 UTCEPSS rescore
  46. 2026-08-11 13:43 UTCVendor advisory
  47. 2026-08-11 13:43 UTCGHSA enrichment
  48. 2026-08-11 00:51 UTCEG score recompute
  49. 2026-08-11 00:51 UTCVendor advisory
  50. 2026-08-11 00:50 UTCGHSA enrichment
  51. 2026-08-11 00:00 UTCEPSS rescore
  52. 2026-08-10 12:43 UTCVendor advisory
  53. 2026-08-10 12:43 UTCGHSA enrichment
  54. 2026-08-10 00:36 UTCEG score recompute
  55. 2026-08-10 00:36 UTCVendor advisory
  56. 2026-08-10 00:36 UTCGHSA enrichment
  57. 2026-08-09 13:47 UTCEPSS rescore
  58. 2026-08-09 12:29 UTCVendor advisory
  59. 2026-08-09 12:29 UTCGHSA enrichment
  60. 2026-08-09 00:11 UTCEG score recompute
  61. 2026-08-09 00:11 UTCVendor advisory
  62. 2026-08-09 00:11 UTCGHSA enrichment
  63. 2026-08-08 16:37 UTCEPSS rescore
  64. 2026-08-08 09:41 UTCVendor advisory
  65. 2026-08-08 09:41 UTCGHSA enrichment
  66. 2026-08-07 21:34 UTCEG score recompute
  67. 2026-08-07 21:34 UTCVendor advisory
  68. 2026-08-07 21:34 UTCGHSA enrichment
  69. 2026-08-07 16:30 UTCEPSS rescore
  70. 2026-08-07 09:27 UTCVendor advisory
  71. 2026-08-07 09:27 UTCGHSA enrichment
  72. 2026-08-06 21:20 UTCEG score recompute
  73. 2026-08-06 21:20 UTCVendor advisory
  74. 2026-08-06 21:20 UTCGHSA enrichment
  75. 2026-08-06 13:47 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-9538?
CVE-2026-9538 is a high vulnerability published on May 26, 2026. Archive::Tar versions before 3.10 for Perl allow memory exhaustion via attacker controlled entry size field in tar header. readtar() reads each entry's payload with $handle->read($$data, $block), where $block is derived from the entry's 12-byte size field in the tar header with no upper bound on…
When was CVE-2026-9538 disclosed?
CVE-2026-9538 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9538 actively exploited?
CVE-2026-9538 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 61.6% of all scored CVEs.
What is the CVSS score of CVE-2026-9538?
CVE-2026-9538 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-9538?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9538, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-9538

Explore →

Is Your Infrastructure Affected by CVE-2026-9538?

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