ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-118763

@sigstore/oci sends the registry Authorization header to a cross-host blob-upload Location

Published Oct 30, 2026 · catalog updated Oct 30, 2026 · @sigstore/oci sends the registry

Last checked Nov 5, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-118763. EPSS is 0.30%. Act only if a listed version of @sigstore/oci sends the registry is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (@sigstore/oci sends the registry).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.30%
Remediation
Version ranges on file
Affected products
npm @sigstore · npm @sigstore/oci

### Summary @sigstore/oci sends the registry Authorization header to a cross-host blob-upload Location ## Affected versions and vulnerable location - Confirmed on sigstore-js at (current HEAD). - File: . - installs the credential as a DEFAULT header on the shared client: ( ) or ( ), plus from the Docker config ( ). - reads the response header ( ), builds ( ), and PUTs the blob to it through the same client: ( ). - There is no check that 's host (or scheme) equals the registry host before the PUT is sent. ## Root cause Because sets via , it is attached to every request the client issues, including requests to a host the client read out of a server response. When a POST to returns an absolute pointing to a different host, PUTs the blob there with the registry header still attached. If the challenge scheme was , that header carries the raw registry ; if bearer, it carries the access token; custom auth headers ride along too. The library's HTTP layer ( / ) strips on cross-host redirects it follows internally, which protects the at . It does not help here, because the PUT to the upload is a fresh, explicit call, not a followed redirect, so the default header is applied unconditionally. This is a residual of GHSA-pf56-329r-95rw / CVE-2026-59891 (credential confusion in ). The fix for that advisory (commit ) changed only , replacing a substring match with an exact host match when SELECTING which Docker credential to load. It never touched , which controls WHERE the loaded credential is sent. The cross-host send remains. ## Attacker model A user pushing a signed artifact/attestation to an OCI registry via . The credential leaks to any host the registry names in the blob-upload . This is reachable when the registry is malicious or compromised, or when a registry that legitimately redirects blob uploads to third-party storage is impersonated. The OCI distribution spec permits absolute upload values (registries commonly redirect blob storage to a separate host), so a compliant

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @sigstoreversion unspecified
  • npm @sigstore/oci0 → 0.7.2
  • npm @sigstore/oci<= 0.7.1

How to fix CVE-2026-118763

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-118763. EPSS is 0.30%. Act only if a listed version of @sigstore/oci sends the registry is installed.

Which versions are affected?

Compare what you have installed with 0 → 0.7.2, <= 0.7.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-522: Insufficiently Protected Credentials. EPSS 0.30%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 30, 2026 · GitHub Advisory Database

    Detected

    ### Summary @sigstore/oci sends the registry Authorization header to a cross-host blob-upload Location ## Affected versions and vulnerable location - Confirmed on sigstore-js at (current HEAD). - File: . - installs the credential as a DEFAULT header on the shared client: ( ) or ( ), plus from the Docker config ( ). - reads the response header ( ), builds ( ), and PUTs the blob to it through the sa

  2. Oct 30, 2026 · GitHub Advisory Database

    Fix available

    @sigstore/oci fixed in 0.7.2

  3. Oct 30, 2026 · GitHub Advisory Database

    Fix available

    @sigstore/oci fixed in 0.7.2

  4. Oct 30, 2026 · GitHub Advisory Database

    Updated

    ### Summary @sigstore/oci sends the registry Authorization header to a cross-host blob-upload Location ## Affected versions and vulnerable location - Confirmed on sigstore-js at (current HEAD). - File: . - installs the credential as a DEFAULT header on the shared client: ( ) or ( ), plus from the Docker config ( ). - reads the response header ( ), builds ( ), and PUTs the blob to it through the sa

Sources

References

Freshness

Last verified in this catalog Nov 3, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitLab Advisory DatabaseNov 5, 2026
  • GitHub Advisory DatabaseNov 4, 2026
  • CVE.orgOct 31, 2026
  • OpenSSF OSV / OSV ScannerOct 31, 2026