CVE-2026-24845: malcontent OCI image pull credential exfiltration via malicious registry token realm

CVE-2026-24845 · Severity: low · CVSS 3.1 · Published 2026-02-19

malcontent OCI image pull credential exfiltration via malicious registry token realm in github.com/chainguard-dev/malcontent

Technologies: github.com/chainguard-dev/malcontent (Go). Vendors: Go.

Quick answers

Is CVE-2026-24845 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-24845 being exploited in the wild.
How severe is CVE-2026-24845?
Low severity, with a CVSS score of 3.1, published 19 February 2026.
Which products and versions are affected?
github.com/chainguard-dev/bincapz (Go) SEMVER:introduced=0.10.0; github.com/chainguard-dev/malcontent (Go) SEMVER:introduced=0,fixed=1.20.3, SEMVER:introduced=0.10.0,fixed=1.20.3.
Is there a fix for CVE-2026-24845?
Yes. github.com/chainguard-dev/malcontent (Go): upgrade to 1.20.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-24845?
Check whether you run github.com/chainguard-dev/bincapz (Go) or github.com/chainguard-dev/malcontent (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/chainguard-dev/malcontent (Go): upgrade to 1.20.3 or later
    go get github.com/chainguard-dev/malcontent@v1.20.3

Affected products

  • github.com/chainguard-dev/bincapz (Go) SEMVER:introduced=0.10.0
  • github.com/chainguard-dev/malcontent (Go) SEMVER:introduced=0,fixed=1.20.3, SEMVER:introduced=0.10.0,fixed=1.20.3

Identifiers

  • CVE-2026-24845
  • GHSA-9m43-p3cx-w8j5
  • GO-2026-4392

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.