@sigstore/oci CVE-2026-118763 (GHSA-j63v-mwhm-56jx): registry Authorization header (credentials or token) sent to a different host from a blob-upload Location response. Am I affected?

What it is: A high-severity advisory published 2026-10-30 for @sigstore/oci, the sigstore-js package that pushes signatures and attestations to OCI container registries. After signing in it attached the registry Authorization header to every request, and when uploading a blob it followed the upload Location returned by the registry without checking that it pointed to the same host. A registry (or anything able to tamper with its responses) that returned an upload location on another host would receive your registry credentials: the raw username and password for Basic auth, or the bearer token. Am I affected: - @sigstore/oci 0.7.1 and earlier (fixed in 0.7.2). It's usually a transitive dependency of sigstore-js tooling used to attach attestations to images in CI. - Check: npm ls @sigstore/oci (or pnpm why / yarn why). - The risk is highest when pushing to registries you don't fully control or through untrusted proxies. Fix: 1. Upgrade so @sigstore/oci resolves to 0.7.2 or later: update the parent packages and lockfile (npm update, or an override/resolution if a parent pins an old version), then rerun CI. 2. Use short-lived, push-scoped registry tokens in CI (for example OIDC-issued tokens) rather than long-lived passwords. 3. If you pushed attestations with an affected version to a registry you don't control, rotate the registry credentials or tokens that were used. Verify: npm ls @sigstore/oci shows only 0.7.2+, and your registry audit log shows no use of old credentials after rotation. Sources: https://github.com/sigstore/sigstore-js/security/advisories/GHSA-j63v-mwhm-56jx https://github.com/sigstore/sigstore-js/releases/tag/@sigstore/oci@0.7.2 https://nvd.nist.gov/vuln/detail/CVE-2026-118763