Malcontent
Approved changes feed: RSS · Atom
cpe:2.3:a:chainguard:malcontent:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Chainguard (ec00b875-0f2e-5e9f-ab7c-43145877d109) |
|---|---|
| Product | Malcontent (ecca3aa1-cad2-50bc-8de2-f27126d3e6fd) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-28407 |
vulnerable | 2026-06-08 07:55:15.262076 |
malcontent's nested archive extraction failure can drop content from scan inputs
malcontent is software for discovering supply-chain compromises through context, differential analysis, and YARA. Prior to version 1.21.0, 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. Version 1.21.0 fixes the issue.
Published: 2026-02-27T21:28:06.258Z
Updated: 2026-03-02T22:01:48.514Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-24846 |
vulnerable | 2026-06-08 07:53:18.323886 |
malcontent's archive extraction could write outside extraction directory
MEDIUM (5.5)
malcontent discovers supply-chain compromises through. context, differential analysis, and YARA. Starting in version 1.8.0 and prior to version 1.20.3, malcontent could be made to create symlinks outside the intended extraction directory when scanning a specially crafted tar or deb archive. The `handleSymlink` function received arguments in the wrong order, causing the symlink target to be used as the symlink location. Additionally, symlink targets were not validated to ensure they resolved within the extraction directory. Version 1.20.3 introduces fixes that swap handleSymlink arguments, validate symlink location, and validate symlink targets that resolve within an extraction directory.
Published: 2026-01-29T21:12:18.991Z
Updated: 2026-01-29T21:37:29.730Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-24845 |
vulnerable | 2026-06-08 07:53:18.322996 |
malcontent's OCI image scanning could expose registry credentials
MEDIUM (6.5)
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.
Published: 2026-01-29T21:02:24.371Z
Updated: 2026-01-29T21:40:17.926Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.