Nixpkgs security tracker

Login with GitHub

Suggestions search

With package: zarf

Found 2 matching suggestions

View:
Compact
Detailed
Published
Permalink CVE-2026-40090
7.1 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): NONE
  • User interaction (UI): REQUIRED
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): NONE
  • Integrity impact (I): HIGH
  • Availability impact (A): LOW
updated 19 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse ignored package idrisPackages.hezarfen
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Zarf has a Path Traversal via Malicious Package Metadata.Name — Arbitrary File Write

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.

Affected products

zarf
  • ==>= 0.23.0, < 0.74.2

Matching in nixpkgs

pkgs.zarf

DevSecOps for Air Gap & Limited-Connection Systems. https://zarf.dev

Ignored packages (1)

Package maintainers

Published
Permalink CVE-2026-29064
8.2 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): LOCAL
  • Attack complexity (AC): LOW
  • Privileges required (PR): NONE
  • User interaction (UI): REQUIRED
  • Scope (S): CHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): HIGH
  • Availability impact (A): NONE
updated 1 month, 1 week ago by @mweinelt Activity log
  • Created automatic suggestion
  • @mweinelt accepted
  • @mweinelt published on GitHub
Zarf: Symlink targets in archives are not validated against destination directory

Zarf is an Airgap Native Packager Manager for Kubernetes. From version 0.54.0 to before version 0.73.1, a path traversal vulnerability in archive extraction allows a specifically crafted Zarf package to create symlinks pointing outside the destination directory, enabling arbitrary file read or write on the system processing the package. This issue has been patched in version 0.73.1.

Affected products

zarf
  • ==>= 0.54.0, < 0.73.1

Matching in nixpkgs

pkgs.zarf

DevSecOps for Air Gap & Limited-Connection Systems. https://zarf.dev

Package maintainers

https://github.com/zarf-dev/zarf/security/advisories/GHSA-hcm4-6hpj-vghm