Advisory record · GHSA-pj97-4p9w-gx3q

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

CVSS 7.1 HighEPSS 0.0033 · 26th percentile

Published by the GitHub Advisory Database at 14 Apr 2026, 22:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/zarf-dev/zarfGo>=0.23.0, <0.74.20.74.2
Identifiers
GHSA-pj97-4p9w-gx3q · CVE-2026-40090 · GO-2026-5542
Weakness (CWE)
CWE-22
Published
14 Apr 2026
Updated
23 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Zarf versions from 0.23.0 before 0.74.2 are vulnerable through the package inspect sbom and package inspect documentation commands when run on untrusted packages. A malicious package can set a crafted metadata name that causes files to be written to arbitrary locations, limited by the permissions of the user running the command. Upgrade to Zarf 0.74.2 or later; as a workaround, avoid inspecting unsigned packages.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.1 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0033, the 26th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:57 UTC First seen by agentprime
  2. 31 Oct 2026, 14:57 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.