NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

malcontent: Error-path cleanup gap can leak scanners and fds and degrade availabilityGHSA-54p8-x2m9-c593

MEDIUMFix: chainguard-dev/malcontent#1354

GHSA-54p8-x2m9-c593 is a medium-severity (CVSS 5.3) vulnerability in github.com/chainguard-dev/malcontent. A fix is available for github.com/chainguard-dev/malcontent — see the affected versions and patch details below.

Also known asGO-2026-4583
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Mar 23, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/chainguard-dev/malcontent

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

Several extraction and scanning code paths registered late defers which could leak resources and exhaust system resources.

This report is an aggregate of these individual reports for the affected code:

AdvisoryAffected File
GHSA-jjgh-mc5q-gch7pkg/action/scan.go
GHSA-mwmf-fxh2-w4x7pkg/archive/deb.go
GHSA-p8j3-rpf5-gwv3pkg/archive/gzip.go
GHSA-qfh4-7f5v-75gqpkg/archive/zlib.go
GHSA-wxxf-r586-5rf5pkg/archive/bzip2.go

Fix: #1354, #1355, #1356, #1361

Acknowledgements

Thank you to Oleh Konko from 1seal for discovering and reporting all six of these issues.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/chainguard-dev/malcontentall versions1.21.0go get github.com/chainguard-dev/malcontent@v1.21.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/chainguard-dev/malcontent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/chainguard-dev/malcontent to 1.21.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-54p8-x2m9-c593 is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

Several extraction and scanning code paths registered late defers which could leak resources and exhaust system resources. This report is an aggregate of these individual reports for the affected code: Advisory | Affected File -- | -- `GHSA-jjgh-mc5q-gch7` | `pkg/action/scan.go` `GHSA-mwmf-fxh2-w4x7` | `pkg/archive/deb.go` `GHSA-p8j3-rpf5-gwv3` | `pkg/archive/gzip.go` `GHSA-qfh4-7f5v-75gq` | `pkg/archive/zlib.go` `GHSA-wxxf-r586-5rf5` | `pkg/archive/bzip2.go` **Fix**: #1354, #1355, #1356, #1361 **Acknowledgements** Thank you to Oleh Konko from [1seal](https://1seal.org/) for discovering an
O3 Security · Impact-Aware SCA

Is GHSA-54p8-x2m9-c593 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
malcontent: Error-path cleanup gap can leak scanners…