{"id":"EUVD-2026-113272","revision":"a5c320d99a9a448e83d8a0d5fa1545a6","records":[{"revision":"a5c320d99a9a448e83d8a0d5fa1545a6","observedAt":"2026-10-30T23:48:15.259+00:00","statement":{"source":"euvd","id":"EUVD-2026-113272","aliases":["CVE-2026-118763"],"title":"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 …","description":"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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N","score":7.4,"severity":null}],"references":["https://github.com/sigstore/sigstore-js/security/advisories/GHSA-j63v-mwhm-56jx","https://github.com/sigstore/sigstore-js/pull/1762","https://github.com/sigstore/sigstore-js/commit/b855f46cfe81f26481c6d3f4b333dfd00f2fd1b1","https://github.com/sigstore/sigstore-js/commit/e4ca65c3ab3c675456ab9b0bd04217ceccad3558","https://github.com/sigstore/sigstore-js/releases/tag/@sigstore/oci@0.7.2"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-113272","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Oct 29, 2026, 5:01:40 PM","dateUpdated":"Oct 30, 2026, 5:13:12 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2026-113272","identifiers":["EUVD-2026-113272","CVE-2026-118763"]},"retained":false,"historicalAffected":[]}],"coverage":[]}