Vulnerability · Published Jul 14, 2026 · Assigned by GitHub_M

CVE-2026-59891Credential confusion in  @sigstore/oci  can leak registry credentials to an attacker-controlled registry

Critical 9.6

In plain English

A critical-severity security flaw in sigstore-js from sigstore. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 41% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code. Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)9.6Critical
Exploit odds (30 days)0.5%top 58.9% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack tooling1Public PoC

Official description

sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 0.7.1, getRegistryCredentials() reads credentials from the Docker config file and selects an entry by checking whether any configured auth key contains the target registry string. Because this is a substring match rather than an exact host match, credentials configured for one registry can be selected for and transmitted to a different registry whose hostname has a substring relationship with a configured auth key. This issue is fixed in version 0.7.1.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npm@sigstore/oci0.7.1GHSA-pf56-329r-95rw

Affected products (as reported)

VendorProductVersions
sigstore sigstore-js < 0.7.1

Weakness: CWE-522 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

References