dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2026-59891

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The getRegistryCredentials() function in sigstore-js uses substring matching to select Docker config credentials for registries. This allows credentials configured for one registry to be inadvertently sent to a different registry whose hostname is a substring of the configured auth key, leading to credential leakage to unintended registries.

MitigationUpgrade sigstore-js to version 0.7.1 or later, which implements exact host matching instead of substring matching for registry credential selection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify sigstore-js installation and version
    Run 'npm list sigstore-js' or check package.json dependencies to determine the installed version of sigstore-js
    Affected if The installed version is earlier than 0.7.1
  2. Locate getRegistryCredentials function usage
    Search project codebase for usage of getRegistryCredentials() function from sigstore-js, typically in files related to Docker registry authentication
    Affected if The function is called and uses Docker config credentials for registry authentication
  3. Examine Docker config.json for registry patterns
    Inspect ~/.docker/config.json or project Docker config files for credential entries. Look for registry hostnames that could be substrings of other registry hostnames (e.g., 'registry.example.com' contains 'gistry.example.com')
    Affected if Multiple registry entries exist where one hostname is a substring of another, and the earlier version (<0.7.1) of sigstore-js is in use
  4. Verify credential behavior with test registry
    If possible, perform a dry-run or trace network requests when authenticating to a registry whose hostname is a substring of another configured registry. Monitor which credentials are actually sent
    Affected if Credentials configured for a different (longer) registry are observed being transmitted to a registry whose hostname is a substring match

A user is affected if sigstore-js version is earlier than 0.7.1 and Docker config contains registry credentials where one hostname is a substring of another configured registry hostname.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade sigstore-js to version 0.7.1 or later, which implements exact host matching instead of substring matching for registry credential selection.

Recommended fix High confidence

sigstore-js version 0.7.1 or later

  1. Check the current version of sigstore-js in your project dependencies (e.g., via package.json or npm list)
  2. Upgrade sigstore-js to version 0.7.1 or later by running: npm install sigstore-js@^0.7.1 (or yarn/pnpm equivalent)
  3. Verify the upgrade was successful and that no other vulnerable versions remain in your dependency tree

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59891 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59891 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data