Sigstore sigstore-js
Credential confusion in @sigstore/oci can leak registry credentials to an attacker-controlled registry
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.7.1
Fixed in 0.7.1
Mitigation
Upgrade sigstore-js to 0.7.1 or later.
References
- Vendor advisory github.com/sigstore/sigstore-js/security/advis…
- Patch github.com/sigstore/sigstore-js/commit/85c5838…
- Release notes github.com/sigstore/sigstore-js/releases/tag/%…
Timeline
Days relative to CVE publicationFirst public PoC 14 days after publication; not in CISA KEV. First PoC: gyubin02/cve-2026-59891-control-lab (created 28 Jul 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| gyubin02/cve-2026-59891-control-lab | 28 Jul 2026 +14 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.