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-24844: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in chainguard-dev melange

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

Description

CVE-2026-24844 is a high-severity OS command injection vulnerability in chainguard-dev's melange tool versions 0. 3. 0 up to but not including 0. 40. 3. The flaw arises when user-controlled input values are substituted into the working-directory field of declarative build pipelines without proper shell escaping, allowing attackers with limited privileges to execute arbitrary shell commands. Exploitation requires the attacker to provide build input values and involves user interaction, but does not require modification of pipeline definitions. The vulnerability impacts confidentiality and integrity but not availability. It has been patched in version 0. 40.

AI-Powered Analysis

Machine-generated threat intelligence

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

Technical Analysis

CVE-2026-24844 is an OS command injection vulnerability classified under CWE-78 affecting the melange tool developed by chainguard-dev, which is used for building APK packages via declarative pipelines. Versions from 0.3.0 up to but not including 0.40.3 are vulnerable. The issue stems from improper neutralization of special shell characters in the working-directory field when the pipeline uses variable substitutions such as ${{vars.*}} or ${{inputs.*}}. These substitutions are embedded directly into shell scripts without adequate quoting or escaping, enabling an attacker who can supply build input values (but cannot alter pipeline definitions) to inject and execute arbitrary shell commands. The vulnerability requires some level of privilege (limited) and user interaction, and it affects the confidentiality and integrity of the build environment by potentially allowing unauthorized command execution. The CVSS v3.1 score is 7.8 (high), reflecting the significant impact and moderate complexity of exploitation. No known exploits in the wild have been reported as of the publication date. The issue was addressed in melange version 0.40.3 by implementing proper escaping and input validation to prevent command injection.

Potential Impact

For European organizations, this vulnerability poses a significant risk especially to those using melange in their build pipelines for Android APK packaging. Successful exploitation could lead to unauthorized command execution within the build environment, potentially exposing sensitive build artifacts, leaking confidential information, or corrupting the integrity of software packages. This could undermine software supply chain security, leading to downstream compromise of applications distributed to end users. Organizations involved in mobile app development, software supply chain management, or those relying on automated build systems are particularly at risk. The impact is amplified in regulated industries or sectors with strict software integrity requirements, such as finance, healthcare, and critical infrastructure. Additionally, the vulnerability could be leveraged for lateral movement or persistence if the build environment is connected to broader enterprise networks.

Mitigation Recommendations

European organizations should immediately upgrade melange to version 0.40.3 or later to apply the official patch that addresses this vulnerability. Until upgrading, organizations should avoid using untrusted or user-supplied input in the working-directory field or any shell-invoked pipeline parameters. Implement strict input validation and sanitization for all build inputs, especially those that influence shell commands or environment variables. Employ least privilege principles for build system users to limit the ability of attackers to supply malicious inputs. Monitor build logs and pipeline executions for anomalous command executions or unexpected shell activity. Consider isolating build environments using containerization or sandboxing to reduce the blast radius of potential exploitation. Finally, integrate security scanning and static analysis tools into the CI/CD pipeline to detect unsafe shell usage patterns.

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: 6983a549f9fa50a62fa8d0c1

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

Last enriched: 2/12/2026, 7:39:43 AM

Last updated: 3/24/2026, 10:29:06 AM

Views: 51

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