CVE-2026-59891

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
9.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
9.6
EG Score
9.6(medium)
EPSS
24.1%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jul 14, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Credential confusion in  @sigstore/oci  can leak registry credentials to an attacker-controlled registry · Advisory · sigstore/sigstore-js · GitHub

https://github.com/sigstore/sigstore-js/security/advisories/GHSA-pf56-329r-95rw
github_commit Patch Available

commit 85c58380758b (sigstore/sigstore-js)

Patch available: sigstore/sigstore-js @sigstore/[email protected] (contains commit 85c58380758b)

https://github.com/sigstore/sigstore-js/commit/85c58380758b97ce1b74ef470e55cc21f9d3aa89

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 0× in last 7d / 0× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 22:58 UTCEG score recompute
  2. 2026-07-15 18:43 UTCEG score recompute
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 14:28 UTCEG score recompute
  6. 2026-07-15 10:14 UTCEG score recompute
  7. 2026-07-15 06:00 UTCEG score recompute
  8. 2026-07-15 01:45 UTCEG score recompute
  9. 2026-07-14 21:30 UTCEG score recompute
  10. 2026-07-14 17:16 UTCEG score recompute
  11. 2026-07-14 17:10 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59891?
CVE-2026-59891 is a critical vulnerability published on July 14, 2026. 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…
When was CVE-2026-59891 disclosed?
CVE-2026-59891 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59891 actively exploited?
CVE-2026-59891 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59891?
CVE-2026-59891 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-59891?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59891, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59891

Explore →

Is Your Infrastructure Affected by CVE-2026-59891?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs