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

CVE-2026-24843 is a high-severity path traversal vulnerability in chainguard-dev's melange tool versions 0. 11. 3 up to before 0. 40. 3. It allows an attacker who can influence the tar stream from a QEMU guest VM to write files outside the intended workspace on the host system. This occurs because the retrieveWorkspace function does not properly validate tar entry paths, enabling directory traversal via '.. /' sequences. Exploitation requires local access to influence the tar stream and some user interaction, but no privileges are needed. The vulnerability can lead to integrity and availability impacts by overwriting or creating arbitrary files on the host.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/12/2026, 07:39:31 UTC

Technical Analysis

CVE-2026-24843 is a path traversal vulnerability classified under CWE-22 found in chainguard-dev's melange, a tool used for building apk packages via declarative pipelines. Versions from 0.11.3 up to but not including 0.40.3 are vulnerable. The vulnerability arises in the retrieveWorkspace function, which extracts tar archive entries without validating that the file paths remain within the designated workspace directory. An attacker capable of influencing the tar stream generated by a QEMU guest virtual machine can craft malicious tar entries containing '../' sequences to traverse directories and write files outside the intended workspace on the host system. This can lead to unauthorized file creation or overwriting, potentially compromising system integrity and availability. The attack vector requires local access to the QEMU guest VM and some user interaction but does not require privileges or authentication. The vulnerability has a CVSS 3.1 score of 8.2, indicating high severity, with an attack vector classified as local, low attack complexity, no privileges required, user interaction needed, and scope changed. Although no known exploits are currently reported in the wild, the risk is significant due to the potential for arbitrary file writes on the host. The issue was patched in melange version 0.40.3 by adding proper path validation to ensure tar entries do not escape the workspace directory.

Potential Impact

For European organizations, this vulnerability poses a significant risk especially for those utilizing melange in their software build pipelines involving QEMU guest VMs. Successful exploitation can lead to unauthorized modification or creation of files on the host system, potentially allowing attackers to alter build artifacts, inject malicious code, or disrupt build processes. This threatens the integrity and availability of critical development infrastructure. Organizations relying on melange for secure and reproducible builds may face supply chain risks if attackers manipulate build outputs. Additionally, if the host system is shared or part of a larger infrastructure, lateral movement or further compromise could occur. The impact is heightened in environments with sensitive or regulated software development, such as financial, telecommunications, or critical infrastructure sectors prevalent in Europe. The requirement for local access limits remote exploitation but insider threats or compromised guest VMs remain a concern.

Mitigation Recommendations

The primary mitigation is to upgrade melange to version 0.40.3 or later, where the vulnerability is patched. Organizations should audit their build environments to identify any instances of melange within the affected version range. Restricting and monitoring access to QEMU guest VMs is critical to prevent unauthorized manipulation of tar streams. Implement strict controls on who can influence build inputs and tar archives. Employ runtime monitoring to detect anomalous file writes outside expected directories during builds. Consider sandboxing or isolating build hosts to limit the impact of potential escapes. Additionally, validate all inputs and outputs in build pipelines and use integrity verification mechanisms on build artifacts. Regularly review and update CI/CD pipeline security policies to incorporate lessons from this vulnerability.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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/12/2026, 7:39:31 AM

Last updated: 3/25/2026, 2:48:09 AM

Views: 25

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses