Zarf has a Path Traversal via Malicious Package Metadata.Name — Arbitrary File Write

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L

EPSS

• CVE-2026-40090: 0.32% estimated exploitation activity in the next 30 days; percentile 25.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact This vulnerability impacts users of zarf package inspect sbom or zarf package inspect documentation on untrusted packages. Patches #4793, now fixed in version v0.74.2 Workarounds Avoid inspecting unsigned packages Description The package inspect sbom and package inspect documentation subcommands construct output file paths by joining a user-controlled output directory with the package's Metadata.Name field, which is attacker-controlled data read from the package archive. The Metadata.Name field is validated against a regex on create, ^[a-z0-9][a-z0-9\-]$, however a malicious user could unarchive a package to change the .Metadata.Name field and the files inside the SBOMS.tar. This would lead to arbitrary file write in a location of the attackers choosing. Neither location sanitizes or validates the package name before using it in the file path. SBOM inspection: Documentation inspection (line 1219): pkgLayout.Pkg.Metadata.Name is read directly from the untrusted package's…

Published by the source

14 Apr 2026, 22:32 UTC

Last modified by the source

24 Apr 2026, 20:42 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pj97-4p9w-gx3q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-40090

Advisory: Zarf has a Path Traversal via Malicious Package Metadata.Name — Arbitrary File Write
IDs: CVE-2026-40090, GHSA-pj97-4p9w-gx3q
Record: https://patchnext.com/advisories/cve-2026-40090 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zarf-dev/zarf 0.74.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zarf-dev/zarf: affected >= 0.23.0, < 0.74.2; fixed in 0.74.2

## Suggested inspection (read-only)
- Go github.com/zarf-dev/zarf: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zarf-dev/zarf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pj97-4p9w-gx3q (GitHub-reviewed advisory GHSA-pj97-4p9w-gx3q lists affected ranges: Go github.com/zarf-dev/zarf >=0.23.0 <0.74.2)

Commands are suggestions: review each one before running it.