CVE-2026-54448

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

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

Trivy is a security scanner. Prior to 0.71.0, when Trivy scans a Helm chart archive (.tgz), its custom tar unpacker reads each entry with io.ReadAll(tr) and no size limit. An attacker who can place a malicious .tgz file in the scanned path can craft a small compressed archive that decompresses to gigabytes, causing the Trivy process to be killed by the OS OOM killer. This vulnerability is fixed in 0.71.0.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
16.2%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 25, 2026
Patch available. Sources: github_pr, github.
github Patch Available

Helm chart tar bomb causes OOM via unbounded io.ReadAll in parser · Advisory · aquasecurity/trivy · GitHub

https://github.com/aquasecurity/trivy/security/advisories/GHSA-q3fv-x8vg-qqm4
github_pr

refactor(misconf): replace custom Helm archive parsing with Helm SDK loaders

Fix merged in aquasecurity/trivy PR #10718 on 2026-05-27 — awaiting tagged release

https://github.com/aquasecurity/trivy/pull/10718

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 42× 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-11 21:48 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 19:57 UTCEG score recompute
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 18:06 UTCEG score recompute
  8. 2026-07-08 16:13 UTCEG score recompute
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-07 14:22 UTCEG score recompute
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 12:24 UTCEG score recompute
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 10:31 UTCEG score recompute
  20. 2026-07-05 02:31 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 08:39 UTCEG score recompute
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 06:48 UTCEG score recompute
Show 17 more
  1. 2026-07-02 04:56 UTCEG score recompute
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 03:05 UTCEG score recompute
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-30 01:13 UTCEG score recompute
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-28 23:22 UTCEG score recompute
  9. 2026-06-28 14:07 UTCEPSS rescore
  10. 2026-06-28 04:56 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-27 21:31 UTCEG score recompute▼ 0.40
  13. 2026-06-27 03:08 UTCEPSS rescore
  14. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 6.5
  15. 2026-06-26 19:40 UTCEG score recompute
  16. 2026-06-25 17:49 UTCEG score recompute
  17. 2026-06-25 17:48 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-54448?
CVE-2026-54448 is a medium vulnerability published on June 25, 2026. Trivy is a security scanner. Prior to 0.71.0, when Trivy scans a Helm chart archive (.tgz), its custom tar unpacker reads each entry with io.ReadAll(tr) and no size limit. An attacker who can place a malicious .tgz file in the scanned path can craft a small compressed archive that decompresses to…
When was CVE-2026-54448 disclosed?
CVE-2026-54448 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54448 actively exploited?
CVE-2026-54448 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54448?
CVE-2026-54448 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-54448?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54448, 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-54448

Explore →

Is Your Infrastructure Affected by CVE-2026-54448?

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

Start Free Scan →Browse All CVEs