Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-24843: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in chainguard-dev melange

0
High
VulnerabilityCVE-2026-24843cvecve-2026-24843cwe-22
Published: Wed Feb 04 2026 (02/04/2026, 19:31:35 UTC)
Source: CVE Database V5
Vendor/Project: chainguard-dev
Product: melange

Description

melange allows users to build apk packages using declarative pipelines. In version 0.11.3 to before 0.40.3, an attacker who can influence the tar stream from a QEMU guest VM could write files outside the intended workspace directory on the host. The retrieveWorkspace function extracts tar entries without validating that paths stay within the workspace, allowing path traversal via ../ sequences. This issue has been patched in version 0.40.3.

AI-Powered Analysis

AILast updated: 02/04/2026, 20:15:53 UTC

Technical Analysis

CVE-2026-24843 is a path traversal vulnerability classified under CWE-22 found in the melange tool developed by chainguard-dev, which is used for building apk packages via declarative pipelines. Versions from 0.11.3 up to but not including 0.40.3 are affected. The vulnerability arises in the retrieveWorkspace function, which extracts files from a tar stream originating from a QEMU guest virtual machine. This function fails to validate that the extracted file paths remain confined within the intended workspace directory on the host. An attacker capable of influencing the tar stream can craft entries containing '../' sequences to traverse directories and write files outside the designated workspace. This can lead to unauthorized modification or overwriting of critical files on the host system, compromising system integrity and potentially causing denial of service. The vulnerability has a CVSS v3.1 score of 8.2, indicating high severity, with an attack vector limited to local (AV:L), low attack complexity (AC:L), no privileges required (PR:N), but requiring user interaction (UI:R). The scope is changed (S:C), impacting integrity and availability but not confidentiality. No known exploits are currently reported in the wild. The issue was publicly disclosed on February 4, 2026, and fixed in melange version 0.40.3.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the integrity and availability of build environments that utilize melange versions prior to 0.40.3, especially those employing QEMU guest VMs. Successful exploitation could allow attackers to write arbitrary files on the host system outside the intended workspace, potentially leading to code execution, system compromise, or disruption of build pipelines. This could affect software supply chain security, undermining trust in produced packages. Organizations relying on melange for apk package creation in critical infrastructure, software development, or embedded systems could face operational disruptions and reputational damage. The requirement for local access to the QEMU guest VM somewhat limits the attack surface but does not eliminate risk, particularly in multi-tenant or shared environments common in European data centers. The vulnerability's ability to alter host files also raises concerns about compliance with European data protection and cybersecurity regulations, such as GDPR and NIS Directive, if exploitation leads to data integrity issues or service outages.

Mitigation Recommendations

The primary mitigation is to upgrade melange to version 0.40.3 or later, where the path traversal vulnerability has been patched by properly validating tar entry paths to ensure they remain within the workspace directory. Until upgrading, organizations should implement strict controls on the tar streams accepted from QEMU guest VMs, including validating and sanitizing inputs to prevent malicious path sequences. Restricting access to QEMU guest VMs to trusted users only and monitoring for suspicious file extraction activities can reduce risk. Employing containerization or sandboxing for build processes can limit the impact of potential exploits. Additionally, auditing build pipelines and host filesystem permissions to minimize the potential damage from unauthorized file writes is recommended. Regularly reviewing and updating security policies around virtualization and build infrastructure will help prevent exploitation. Finally, integrating file integrity monitoring on host systems can detect unauthorized changes resulting from exploitation attempts.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-27T14:51:03.059Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6983a549f9fa50a62fa8d0bd

Added to database: 2/4/2026, 8:00:09 PM

Last enriched: 2/4/2026, 8:15:53 PM

Last updated: 2/7/2026, 7:59:06 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats