Unrated

Incomplete package integrity verification in melange/apko

IdentifiersCVE-2026-54174CWE-353

CVE-2026-54174 is an integrity verification flaw in melange and apko in which package verification does not fully protect the package data section. As a result, verification of the package control section can still succeed even if the package payload has been substituted. This creates a gap between what is authenticated and what is ultimately installed, allowing tampering with package contents without detection during normal verification.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to cause installation of arbitrary substituted package contents while integrity checks still appear to pass. This undermines trust in the software supply chain and can result in unauthorized code or files being installed on affected systems, potentially leading to execution of attacker-controlled content, persistence, or broader compromise depending on the privileges and role of the affected package.

Mitigation

If you can’t patch tonight, do this now.

Until patched versions can be deployed, reduce exposure by retrieving packages only through strongly trusted channels, minimizing reliance on untrusted mirrors and intermediary caches, and protecting package transport against interception or tampering. Environments with elevated supply-chain risk should treat packages obtained through potentially compromised distribution paths as untrusted and re-fetch or rebuild them after remediation.

Remediation

Patch, then assume compromise.

Upgrade chainguard.dev/apko to version 1.2.9 or later and chainguard.dev/melange to version 0.50.4 or later, which address the incomplete integrity verification condition. After upgrading, rebuild or reinstall affected artifacts as appropriate to ensure previously retrieved or generated packages are not trusted if they may have traversed an untrusted mirror, cache, or network path.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

ChainguardApkoapplication

ChainguardMelangeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity