CVE-2026-40090 json
Zarf has a Path Traversal via Malicious Package Metadata.Name — Arbitrary File Write
published 2026-04-14 6 mo ago modified 2026-07-23 3 mo ago also EUVD-2026-22814 , GHSA-pj97-4p9w-gx3q , GO-2026-5542
- cvss
- 7.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
Zarf is an Airgap Native Packager Manager for Kubernetes. Versions 0.23.0 through 0.74.1 contain an arbitrary file write vulnerability in the zarf package inspect sbom and zarf package inspect documentation subcommands. These subcommands output file paths are constructed by joining a user-controlled output directory with the package's Metadata.Name field read directly from the untrusted package's zarf.yaml manifest. Although Metadata.Name is validated against a regex on package creation, an attacker can unarchive a package to modify the Metadata.Name field to contain path traversal sequences such as ../../etc/cron.d/malicious or absolute paths like /home/user/.ssh/authorized_keys, along with the corresponding files inside SBOMS.tar. This allows writing attacker-controlled content to arbitrary filesystem locations within the permissions of the user running the inspect command. This issue has been fixed in version 0.74.2.
Patch / fix
- go github.com/zarf-dev/zarf 0.74.2
- lfprojects zarf 0.74.2
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L |
| GitHub | 3.1 | 7.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/zarf-dev/zarf | >=0.23.0, <0.74.2 >=0.37.0, <0.74.2 |
0.74.2 |
| go | github.com/defenseunicorns/zarf | >=0.23.0 |
no fix listed |
Affected products
- zarf-dev zarf
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/zarf-dev/zarf/pull/4793
web, issue-tracking, patch
-
github.com
/zarf-dev/zarf/security/advisories/GHSA-pj97-4p9w-gx3q
web, patch, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-40090
advisory
-
github.com
/zarf-dev/zarf
package
Sources
- CVE List CVE-2026-40090
- GitHub Advisory GHSA-pj97-4p9w-gx3q
- NVD CVE-2026-40090
- OSV GO-2026-5542
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.