Critical severity · published Jul 14, 2026
CVE-2026-59891
Credential confusion in @sigstore/oci can leak registry credentials to an attacker-controlled registry
9.6
CVSS
0.5%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
High
Integrity
High
Availability
High
Scope
Changed
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 41% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SI
sigstore-js · sigstore
< 0.7.1 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-59891
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-59891
github.com
https://github.com/sigstore/sigstore-js/commit/85c58380758b97ce1b74ef470e55cc21f9d3aa89
github.com
https://github.com/sigstore/sigstore-js/releases/tag/%40sigstore%2Foci%400.7.1
github.com
https://github.com/sigstore/sigstore-js/security/advisories/GHSA-pf56-329r-95rw
More from sigstore-js
7.5
CVE-2026-48815
sigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforced
6.5
CVE-2026-48816
sigstore-js: Insufficient Verification of Data Authenticity
5.4
CVE-2026-48758
sigstore-js: DSSE payloadType type-binding failure
