Nixpkgs security tracker

Login with GitHub

Details of issue NIXPKGS-2026-0095

NIXPKGS-2026-0095
published on
Permalink CVE-2026-25145
5.5 MEDIUM
  • CVSS version: 3.1
  • Attack vector (AV): LOCAL
  • Attack complexity (AC): LOW
  • Privileges required (PR): NONE
  • User interaction (UI): REQUIRED
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): NONE
  • Availability impact (A): NONE
updated 2 months, 3 weeks ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored
    6 packages
    • ocamlPackages.melange
    • ocamlPackages.melange-json
    • ocamlPackages_latest.melange
    • ocamlPackages.melange-json-native
    • ocamlPackages_latest.melange-json
    • ocamlPackages_latest.melange-json-native
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
melange has a path traversal in license-path which allows reading files outside workspace

melange allows users to build apk packages using declarative pipelines. From version 0.14.0 to before 0.40.3, an attacker who can influence a melange configuration file (e.g., through pull request-driven CI or build-as-a-service scenarios) could read arbitrary files from the host system. The LicensingInfos function in pkg/config/config.go reads license files specified in copyright[].license-path without validating that paths remain within the workspace directory, allowing path traversal via ../ sequences. The contents of the traversed file are embedded into the generated SBOM as license text, enabling exfiltration of sensitive data through build artifacts. This issue has been patched in version 0.40.3.

Affected products

melange
  • ==>= 0.14.0, < 0.40.3

Matching in nixpkgs

Ignored packages (6)

Package maintainers

Upstream advisory: https://github.com/chainguard-dev/melange/security/advisories/GHSA-2w4f-9fgg-q2v9
Upstream patch: https://github.com/chainguard-dev/melange/commit/2f95c9f4355ed993f2670bf1bb82d88b0f65e9e4