CVE-2026-59891

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
The EG Score, 9.6 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

July 21, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

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

Vendor Advisories for CVE-2026-59891(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@sigstore/oci—
  • every version up to 0.7.1: fixed in 0.7.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 142 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 42 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 09:14 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-13 06:21 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-12 15:52 UTCEG score recompute
  6. 2026-10-11 19:36 UTCEG score recompute
  7. 2026-10-11 16:51 UTCEG score recompute
  8. 2026-10-11 14:13 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-10-01 13:22 UTCEG score recompute
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-09-28 09:20 UTCEG score recompute
  25. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Show 75 more
  1. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  2. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  3. 2026-09-24 09:51 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-09-23 03:54 UTCEG score recompute
  6. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-09-18 04:53 UTCEG score recompute
  9. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-09-13 23:27 UTCEG score recompute
  14. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-09-13 07:53 UTCEG score recompute
  16. 2026-09-12 01:45 UTCEG score recompute
  17. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-09-08 01:44 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-09-06 19:05 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-09-05 21:17 UTCEG score recompute
  25. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  26. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  27. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  28. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-08-30 20:31 UTCEG score recompute
  30. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  31. 2026-08-30 05:19 UTCEG score recompute
  32. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  33. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  34. 2026-08-27 21:33 UTCEG score recompute
  35. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  36. 2026-08-26 23:36 UTCEG score recompute
  37. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  38. 2026-08-25 19:12 UTCEG score recompute
  39. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  40. 2026-08-24 19:49 UTCEG score recompute
  41. 2026-08-24 13:34 UTCEG score recompute
  42. 2026-08-23 02:39 UTCEG score recompute
  43. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  44. 2026-08-22 01:11 UTCEG score recompute
  45. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  46. 2026-08-20 23:07 UTCEG score recompute
  47. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  48. 2026-08-20 00:32 UTCEG score recompute
  49. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  50. 2026-08-18 20:04 UTCEG score recompute
  51. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  52. 2026-08-17 16:45 UTCEG score recompute
  53. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  54. 2026-08-16 15:06 UTCEG score recompute
  55. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  56. 2026-08-16 02:22 UTCEG score recompute
  57. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-08-15 04:59 UTCEG score recompute
  59. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  60. 2026-08-13 23:15 UTCEG score recompute
  61. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  62. 2026-08-12 17:31 UTCEG score recompute
  63. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  64. 2026-08-11 16:02 UTCEG score recompute
  65. 2026-08-11 03:18 UTCEG score recompute
  66. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  67. 2026-08-09 17:21 UTCEG score recompute
  68. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  69. 2026-08-08 20:08 UTCEG score recompute
  70. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  71. 2026-08-07 18:39 UTCEG score recompute
  72. 2026-08-06 17:04 UTCEG score recompute
  73. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  74. 2026-08-05 19:52 UTCEG score recompute
  75. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59891?
CVE-2026-59891 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-59891 published?
The CVE record for CVE-2026-59891 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 21, 2026; the record at its source may have been updated since.
Is CVE-2026-59891 actively exploited?
CVE-2026-59891 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59891?
CVE-2026-59891 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-59891?
A fix for CVE-2026-59891 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-59891 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs