CVE-2026-24845
malcontent discovers supply-chain compromises through. context, …
malcontent discovers supply-chain compromises through. context, differential analysis, and YARA. Starting in version 0.10.0 and prior to version 1.20.3, malcontent could be made to expose Docker registry credentials if it scanned a specially crafted OCI image reference. malcontent uses google/go-containerregistry for OCI image pulls, which by default uses the Docker credential keychain. A malicious registry could return a `WWW-Authenticate` header redirecting token authentication to an attacker-controlled endpoint, causing credentials to be sent to that endpoint. Version 1.20.3 fixes the issue by defaulting to anonymous auth for OCI pulls.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/chainguard-dev/malcontent/commit/538ed00cdc639d687a4bd1e843a2be0428a3b3e7
- github.com/chainguard-dev/malcontent/security/advisories/GHSA-9m43-p3cx-w8j5
- nvd.nist.gov/vuln/detail/CVE-2026-24845
- github.com/advisories/GHSA-9m43-p3cx-w8j5
- nvd.nist.gov/vuln/detail/CVE-2026-24845
- cve.org/CVERecord?id=CVE-2026-24845
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.