How severe is GHSA-q3fv-x8vg-qqm4?

No CVSS score has been assigned to GHSA-q3fv-x8vg-qqm4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q3fv-x8vg-qqm4?

GHSA-q3fv-x8vg-qqm4 affects the following packages: github.com/aquasecurity/trivy (Go). Ecosystems affected: Go.

How do I fix GHSA-q3fv-x8vg-qqm4?

Update github.com/aquasecurity/trivy to 0.71.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q3fv-x8vg-qqm4 is resolved across your whole dependency graph.

How do I detect GHSA-q3fv-x8vg-qqm4 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/aquasecurity/trivy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-q3fv-x8vg-qqm4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-q3fv-x8vg-qqm4?

O3 pinpoints whether GHSA-q3fv-x8vg-qqm4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-q3fv-x8vg-qqm4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q3fv-x8vg-qqm4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q3fv-x8vg-qqm4?

GHSA-q3fv-x8vg-qqm4 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q3fv-x8vg-qqm4?

GHSA-q3fv-x8vg-qqm4 is classified as CWE-770 (CWE-770), CWE-789 (CWE-789). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q3fv-x8vg-qqm4 published, and has it been updated?

GHSA-q3fv-x8vg-qqm4 was published on July 14, 2026 and was last updated on July 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-q3fv-x8vg-qqm4

Fix: aquasecurity/trivy#10718

GHSA-q3fv-x8vg-qqm4 is a CWE-770 vulnerability in github.com/aquasecurity/trivy. O3 Security confirms whether GHSA-q3fv-x8vg-qqm4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2026-54448GO-2026-5983

Published

Jul 14, 2026

Updated

Jul 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-q3fv-x8vg-qqm4.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹github.com/aquasecurity/trivy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 config . on a repository where a contributor can submit a pull request containing a crafted chart archive.
A pipeline that scans a container image with --scanners misconf, whose build context includes untrusted .tgz files.

Impact

An attacker who satisfies the conditions above can exhaust all available memory on the host running Trivy. The OS OOM killer will terminate the Trivy process and may affect other processes sharing the same host or CI runner.

The practical impact in CI environments is denial of service: the scan fails, the pipeline is blocked, and repeated submissions re-trigger the same condition. Cloud CI runners may also incur additional costs for consumed resources.

There is no impact on confidentiality or integrity of the scanned system.

Patches

Fixed in Trivy v0.71.0 (#10718). The custom tar unpacker was replaced with archive.LoadArchiveFiles from the official helm.sh/helm/v4 SDK, which enforces per-entry and total size limits and validates archive structure. Users should upgrade to v0.71.0 or later.

Workarounds

If upgrading is not immediately possible:

Set a memory limit (cgroup/container) on the Trivy process to bound the blast radius.
Use --skip-dirs to exclude directories containing untrusted Helm chart archives from the scan.
Avoid scanning repositories or images with untrusted .tgz files.

Credits

Reported by @jamesgol.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/aquasecurity/trivy`	all versions	0.71.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/aquasecurity/trivy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/aquasecurity/trivy to 0.71.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q3fv-x8vg-qqm4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-q3fv-x8vg-qqm4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-q3fv-x8vg-qqm4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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>` | Dir

O3 Security · Impact-Aware SCA

Is GHSA-q3fv-x8vg-qqm4 in your dependencies?

O3 detects GHSA-q3fv-x8vg-qqm4 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-q3fv-x8vg-qqm4

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

Real-World Exposure

Description

Summary

Affected configurations

Impact

Patches

Workarounds

Credits

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-q3fv-x8vg-qqm4 in your dependencies?