Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-945p-3jhm-6rcp

malcontent: Nested archive extraction failure can drop content from scan inputs

Also known asCVE-2026-28407GO-2026-4577
Published
Feb 28, 2026
Updated
Mar 23, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk13th percentile+0.19%
0.00%0.24%0.48%0.72%0.0%0.0%0.0%0.0%0.2%Mar 26May 26Jun 26

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.

Blast Radius

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

Previously, malcontent would remove nested archives which failed to extract which could potentially leave malicious content. A better approach is to preserve these archives so that malcontent can attempt a best-effort scan of the archive bytes.

Fix: https://github.com/chainguard-dev/malcontent/pull/1383

Acknowledgements

malcontent thanks Oleh Konko from 1seal for discovering and reporting this issue.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/chainguard-dev/malcontentall versions1.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. 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.

  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-945p-3jhm-6rcp 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-945p-3jhm-6rcp 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-945p-3jhm-6rcp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Previously, malcontent would remove nested archives which failed to extract which could potentially leave malicious content. A better approach is to preserve these archives so that malcontent can attempt a best-effort scan of the archive bytes. **Fix**: https://github.com/chainguard-dev/malcontent/pull/1383 **Acknowledgements** malcontent thanks Oleh Konko from [1seal](https://1seal.org/) for discovering and reporting this issue.
O3 Security · Impact-Aware SCA

Is GHSA-945p-3jhm-6rcp in your dependencies?

O3 detects GHSA-945p-3jhm-6rcp across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.