Nixpkgs Security Tracker

Login with GitHub

Details of issue NIXPKGS-2026-0081

NIXPKGS-2026-0081
published on 23 Jan 2026
updated 4 weeks, 1 day ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    3 packages
    • rekor-cli
    • python312Packages.sigstore-rekor-types
    • python313Packages.sigstore-rekor-types
  • @LeSuisse removed
    2 maintainers
    • @developer-guy
    • @06kellyjac
  • @LeSuisse added
    2 maintainers
    • @fabaff
    • @Bot-wxt1221
  • @LeSuisse removed
    3 maintainers
    • @LeSuisse
    • @Bot-wxt1221
    • @fabaff
  • @LeSuisse added maintainer @LeSuisse
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL

Rekor is a software supply chain transparency log. In versions 1.4.3 and below, attackers can trigger SSRF to arbitrary internal services because /api/v1/index/retrieve supports retrieving a public key via user-provided URL. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. The issue has been fixed in version 1.5.0. To workaround this issue, disable the search endpoint with --enable_retrieve_api=false.

Affected products

rekor
  • ==< 1.5.0

Matching in nixpkgs

Package maintainers

Ignored maintainers (2)
https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j