CVE-2026-118763sigstore-js Insufficiently Protected Credentials
NVDCVSS scored by security-advisories@github.com
Vulnerability Summary
sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 0.7.2, packages/oci/src/registry.ts contains a RegistryClient.signIn() method that stores registry Authorization and Docker configuration headers as defaults on a shared HTTP client, while RegistryClient.uploadBlob() sends a fresh PUT to an absolute blob-upload Location supplied by the registry without checking that its origin or scheme matches the registry. A malicious or compromised registry can therefore direct a user pushing an artifact through attachArtifactToImage() to an attacker-controlled host and receive the registry bearer token, Basic credentials, or custom authentication headers. Redirect-time header stripping does not prevent the leak because the cross-host PUT is a new explicit request rather than a followed redirect. This is a residual of CVE-2026-59891, whose fix changed credential selection in credentials.ts but did not constrain where credentials are sent from registry.ts. Version 0.7.2 fixes the issue by separating registry credentials from client-wide defaults and sending them only to the registry origin.
CVSS v3.1 Base Metrics — Score 7.4 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:NAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone
Affected & Patched Versions
- sigstore-js < 0.7.2
No patched version published yet
Until a fix ships, reduce exposure:
- Restrict access to the affected service or interface to trusted networks.
- Disable the affected feature if you do not need it.
- Watch the vendor advisory for a firmware or software update.
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run sigstore-js and which version.
- No patched version is listed yet. Limit access to the affected service to trusted networks, and disable the feature if you can.
- Subscribe to the vendor advisory so you learn when a fix ships.
Timeline
- Oct 29, 2026Published
- Oct 30, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new sigstore-js CVEsYou are reading CVE-2026-118763. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore sigstore-js CVEs
External References
- Patchhttps://github.com/sigstore/sigstore-js/commit/b855f46cfe81f26481c6d3f4b333dfd00f2fd1b1
- Patchhttps://github.com/sigstore/sigstore-js/commit/e4ca65c3ab3c675456ab9b0bd04217ceccad3558
- Patchhttps://github.com/sigstore/sigstore-js/pull/1762
- Referencehttps://github.com/sigstore/sigstore-js/releases/tag/@sigstore/oci@0.7.2
- Vendor Advisoryhttps://github.com/sigstore/sigstore-js/security/advisories/GHSA-j63v-mwhm-56jx
Data last checked: Nov 22, 2026 23:12 UTC