Vulnary
← back to the feed
Critical· 9.6official fix available

CVE-2026-59891

sigstore-js is a JavaScript library that helps developers interact with Sigstore services. In versions before 0.7.1, the library incorrectly matched registry credentials by substring, which could cause credentials for one registry to be sent to another. This flaw allows an attacker to obtain and misuse private registry credentials.

publishedJul 14, 2026
last modifiedJul 21, 2026
sourcesNVD
severity · cvss
9.6
critical · how bad it is
exploitation · epss
<1%
24th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 20, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

sigstore-js library, any project using it with a version earlier than 0.7.1. Developers or CI/CD pipelines that rely on this library to pull or push container images.

02

Real-world impact

An attacker who can influence the registry selection could capture the credentials stored in the Docker config file and use them to access private images, push malicious images, or otherwise compromise the registry’s security.

03

Why this severity

The CVSS score of 9.6 reflects a network‑based attack that requires no special privileges and only a user interface to trigger. Because the flaw can expose all confidentiality, integrity, and availability of the registry, the impact is rated high for all three metrics.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade sigstore-js to version 0.7.1 or later.

NVD-referenced vendor advisory

05

Timeline

  1. Jul 14, 2026 · 20d ago
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 21, 2026 · 13d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 21, 2026 · 13d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeChanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →