CVE-2026-25143: melange affected by potential host command execution via license-check YAML mode patch pipeline

Published Feb 4, 2026
·
Updated

An attacker who can influence inputs to the patch pipeline could execute arbitrary shell commands on the build host. The patch pipeline in pkg/build/pipelines/patch.yaml embeds input-derived values (series paths, patch filenames, and numeric parameters) into shell scripts without proper quoting or validation, allowing shell metacharacters to break out of their intended context. The vulnerability affects the built-in patch pipeline which can be invoked through melange build and melange license-check operations. An attacker who can control patch-related inputs (e.g., through pull request-driven CI, build-as-a-service, or by influencing melange configurations) can inject shell metacharacters such as backticks, command substitutions $(…), semicolons, pipes, or redirections to execute arbitrary commands with the privileges of the melange build process.

Fix: Fixed in bd132535 , Released in 0.40.3. Acknowledgements melange thanks Oleh Konko (@1seal) from 1seal for discovering and reporting this issue.

Other sources

melange allows users to build apk packages using declarative pipelines. From version 0.10.0 to before 0.40.3, an attacker who can influence inputs to the patch pipeline could execute arbitrary shell commands on the build host. The patch pipeline in pkg/build/pipelines/patch.yaml embeds input-derived values (series paths, patch filenames, and numeric parameters) into shell scripts without proper quoting or validation, allowing shell metacharacters to break out of their intended context. The vulnerability affects the built-in patch pipeline which can be invoked through melange build and melange license-check operations. An attacker who can control patch-related inputs (e.g., through pull request-driven CI, build-as-a-service, or by influencing melange configurations) can inject shell metacharacters such as backticks, command substitutions $(…), semicolons, pipes, or redirections to execute arbitrary commands with the privileges of the melange build process. This issue has been patched in version 0.40.3.

— MITRE

Affected Software

2 affected componentsFixes available
go/chainguard.dev/melange>=0.10.0<0.40.3
0.40.3
chainguard Melange Go>=0.10.0<0.40.5

Event History

Feb 4, 2026
Advisory Published
via GitHub·12:09 AM
Data Sourced
via GitHub·12:09 AM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·07:32 PM
Data Sourced
via MITRE·07:32 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
RemedyAffected Software
Nov 23, 58106
Event
via FIRST·11:05 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-25143?

CVE-2026-25143 has been classified as a critical vulnerability due to the potential for arbitrary code execution on the build host.

2

How do I fix CVE-2026-25143?

To mitigate CVE-2026-25143, upgrade to version 0.40.3 or later of the affected software.

3

What software is affected by CVE-2026-25143?

CVE-2026-25143 specifically affects the chainguard.dev/melange package versions between 0.10.0 and 0.40.3.

4

What type of attack does CVE-2026-25143 facilitate?

CVE-2026-25143 could allow an attacker to execute arbitrary shell commands on the build host by influencing inputs to the patch pipeline.

5

What are the implications of CVE-2026-25143?

The implications of CVE-2026-25143 include potential full system compromise if an attacker can exploit the vulnerability to run arbitrary commands.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203