sigstore sigstore-js up to 0.7.0 Registry Credential Matcher getRegistryCredentials Hostname information disclosure

Summaryinfo

A vulnerability was found in sigstore sigstore-js up to 0.7.0. It has been classified as problematic. Affected is the function getRegistryCredentials of the component Registry Credential Matcher. The manipulation of the argument Hostname leads to information disclosure. This vulnerability is traded as CVE-2026-59891. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in sigstore sigstore-js up to 0.7.0 and classified as problematic. This issue affects the function getRegistryCredentials of the component Registry Credential Matcher. The manipulation of the argument hostname with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-59891 since 07/07/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 0.7.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• sigstore

Name

• sigstore-js

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7.0

Website

• Product: https://github.com/sigstore/sigstore-js/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion