Technical impact
sigstore-js stores authentication cookies and Docker configuration headers on a shared HTTP client and then sends those headers to any absolute blob‑upload location supplied by the registry without verifying that the target host matches the registry origin; this flaw aligns with CWE‑201 Information Exposure and CWE‑522 Insufficiently Protected Credentials and allows a malicious or compromised registry to redirect a client during artifact upload and capture bearer tokens, Basic credentials, or custom authentication headers.
Affected Systems
The vulnerable component is the sigstore-js JavaScript library, used to interact with Sigstore services. All releases prior to 0.7.2 of the sigstore:sigstore-js product are affected; version 0.7.2 fixes the issue by separating registry credentials from client‑wide defaults and ensuring they are only sent to the registry origin.
Risk and Exploitability
With a CVSS score of 7.4 (high) and an EPSS score of < 1%, the likelihood of exploitation is low but nonzero; the vulnerability is not listed in the CISA KEV catalog. The attack vector is remote, requiring an attacker to control or manipulate the registry’s upload URL. Once the cross‑host PUT is performed, the attacker can obtain critical authentication material and potentially access protected resources or services.
Github GHSA