● Medium · CVSS 6.1

How to Fix CVE-2026-29050: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Q: Is CVE-2026-29050 being exploited in the wild?

As of 2026-05-25, CVE-2026-29050 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

Q: What is the CVSS score for CVE-2026-29050?

The CVSS base score is 6.1 (Medium).

Q: What version fixes this?

The vendor advisory names the patched build. See the References section.

Q: Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

By Sai Kiran Pandrala

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-2332: Inconsistent interpretation of http requests in Eclipse Jetty — Inconsistent interpretation of http requests in Eclipse Jetty
How to Fix CVE-2026-5339: Tenda G103 Setting gpon.lua action_set_net_settings command injection — Tenda G103 Setting gpon.lua action_set_net_settings command injection
How to Fix CVE-2026-4956: SQL Injection in Streamax Crocus , SQL Injection in Streamax Crocus
How to Fix CVE-2026-25612: Critical Vulnerability in MongoDB Server , Critical Vulnerability in MongoDB Server
How to Fix CVE-2026-28766: Cloud API (Bundle Sibling) , Cloud API (Bundle Sibling)

Last verified: 2026-05-25

CVE-2026-29050 is a cwe-22: improper limitation of a pathname to a restricted directory ('path traversal') in chainguard-dev melange. Fix it by upgrading to the patched build from the vendor advisory.

⚡ At a glance


Severity	CVSS 6.1 - Medium
Actively exploited?	Not currently in the CISA KEV catalog
Affected	melange >= 0.32.0, < 0.43.4
Fixed in	See vendor advisory
Type (CWE)	CWE-22: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-29050?

CVE-2026-29050 is a cwe-22: improper limitation of a pathname to a restricted directory ('path traversal') flaw in chainguard-dev melange. It carries a CVSS base score of 6.1 (medium). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: melange allows users to build apk packages using declarative pipelines. Starting in version 0.32.0 and prior to version 0.43.4, an attacker who can influence a melange configuration file, for example through pull-request-driven CI or build-as-a-service scenarios, could set pipeline[].uses to a value containing ../ sequences or an absolute path. The (*Compiled).compilePipeline function in pkg/build/compile.go passed uses directly to filepath.Join(pipelineDir, uses + ".yaml") without validating the value, so the resolved path could escape each --pipeline-dir and read an arbitrary YAML-parseable file visible to the melange process.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of melange matches a version listed in the Affected row above.

Check the running version against the Affected row above using the product's admin console or --version flag.

How to fix CVE-2026-29050

Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for melange.

Generic upgrade pattern

If the affected product is a Linux package, upgrade via the system package manager:


# Debian / Ubuntu
sudo apt-get update && sudo apt-get upgrade -y

# RHEL / Rocky / Alma
sudo dnf upgrade --security -y

If it ships as a Windows installer, download the patched build from the vendor advisory and:


# Vendor advisory: https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9
Start-Process msiexec.exe -ArgumentList '/i <patched-installer>.msi /qn /norestart' -Wait
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | \
    Where-Object DisplayName -match '<product-name>' | Select-Object DisplayName, DisplayVersion

After applying the patch

Restart the service or device so the patched binary loads.
Confirm the running version matches the Fixed in row using the verification command below.
Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.


# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4


# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

Check the running version against the Affected row above using the product's admin console or --version flag.

Expected: a version at or above the patched build named in the vendor advisory.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-29050 being exploited in the wild?