LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28407: 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.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-28407 affects malcontent, a tool used to detect supply-chain compromises. Before version 1.21.0, if a nested archive failed to extract, malcontent removed it from scan inputs. That could allow suspicious content inside the archive to be missed. This is a detection-gap issue, not direct code execution.

Executive priority

Prioritize where malcontent informs release, package intake, or incident triage decisions. This does not appear to enable direct system compromise, but it can weaken supply-chain detection confidence. Upgrade during the next security maintenance window, sooner for critical scanning pipelines.

Technical view

Affected malcontent versions before 1.21.0 mishandle nested archive extraction failures. Instead of preserving failed nested archives for best-effort byte scanning, the tool removes them, potentially excluding malicious content from analysis. The CVE maps to CWE-703 and has CVSS 4.0 score 6.9. Version 1.21.0 fixes the behavior.

Likely exposure

Exposure is limited to organizations using malcontent versions earlier than 1.21.0, especially in supply-chain scanning, package review, or CI security workflows that process nested archives.

Exploitation context

No source in the bundle reports active exploitation, and the CVE is not marked KEV. The risk is that crafted or problematic nested archives could reduce scanner coverage and create false negatives during malware or supply-chain compromise detection.

Researcher notes

The key behavior change is preservation of failed nested archives for best-effort scanning instead of removal. Public sources identify the affected range as prior to 1.21.0 and the fix in 1.21.0. Evidence does not include exploit details or active exploitation claims.

Mitigation direction

  • Upgrade malcontent to version 1.21.0 or later.
  • Review vendor advisory and release notes before deployment.
  • Re-scan high-risk artifacts previously analyzed with affected versions.
  • Check CI and security-tooling images for embedded vulnerable malcontent versions.

Validation and detection

  • Inventory malcontent installations and confirm versions are 1.21.0 or later.
  • Review scan logs for nested archive extraction failures in prior analyses.
  • Confirm updated scans preserve or best-effort analyze failed nested archives.
  • Validate container images or build runners do not pin malcontent below 1.21.0.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-703: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-28407 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-28407Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
chainguard-devmalcontent< 1.21.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-703 · source CWE mapping

Improper Check or Handling of Exceptional Conditions

Improper Check or Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.