Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

Trivy: Helm chart tar bomb causes OOM via unbounded io.ReadAll in parser

CVE-2026-54448GHSA-q3fv-x8vg-qqm4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/aquasecurity/trivy 0.71.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-54448: 0.44% estimated exploitation activity in the next 30 days; percentile 38.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Affected configurations Exploitation requires the attacker to place a crafted .tgz file in a location that Trivy will scan as a Helm chart. This applies to the following scan targets: | Command | Condition | | --- | --- | | trivy config <dir | Directory contains a crafted .tgz Helm chart (misconfiguration scanning is always enabled) | | trivy filesystem --scanners misconf <dir | Directory contains a crafted .tgz Helm chart and --scanners misconf is explicitly enabled | | trivy image --scanners misconf <image | Image contains a crafted .tgz Helm chart and --scanners misconf is explicitly enabled | Realistic scenarios include: - A CI pipeline that runs trivy…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-q3fv-x8vg-qqm4

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GO-2026-5983

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54448

Advisory: Trivy: Helm chart tar bomb causes OOM via unbounded io.ReadAll in parser
IDs: CVE-2026-54448, GHSA-q3fv-x8vg-qqm4
Record: https://patchnext.com/advisories/cve-2026-54448 (revision 3, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/aquasecurity/trivy 0.71.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/aquasecurity/trivy: affected < 0.71.0; fixed in 0.71.0

## Suggested inspection (read-only)
- Go github.com/aquasecurity/trivy: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/aquasecurity/trivy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-5983 (OSV record GO-2026-5983 lists affected ranges: Go github.com/aquasecurity/trivy >=0 <0.71.0 (fixed))
- Verified: https://github.com/advisories/GHSA-q3fv-x8vg-qqm4 (GitHub-reviewed advisory GHSA-q3fv-x8vg-qqm4 lists affected ranges: Go github.com/aquasecurity/trivy >=0 <0.71.0)

Commands are suggestions: review each one before running it.

Loading voting…