CVE-2026-118763

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

Published Oct 29, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

sigstore-js stores authentication cookies and Docker configuration headers on a shared HTTP client and then sends those headers to any absolute blob‑upload location supplied by the registry without verifying that the target host matches the registry origin; this flaw aligns with CWE‑201 Information Exposure and CWE‑522 Insufficiently Protected Credentials and allows a malicious or compromised registry to redirect a client during artifact upload and capture bearer tokens, Basic credentials, or custom authentication headers.

Affected Systems

The vulnerable component is the sigstore-js JavaScript library, used to interact with Sigstore services. All releases prior to 0.7.2 of the sigstore:sigstore-js product are affected; version 0.7.2 fixes the issue by separating registry credentials from client‑wide defaults and ensuring they are only sent to the registry origin.

Risk and Exploitability

With a CVSS score of 7.4 (high) and an EPSS score of < 1%, the likelihood of exploitation is low but nonzero; the vulnerability is not listed in the CISA KEV catalog. The attack vector is remote, requiring an attacker to control or manipulate the registry’s upload URL. Once the cross‑host PUT is performed, the attacker can obtain critical authentication material and potentially access protected resources or services.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade sigstore-js to version 0.7.2 or later, which separates registry credentials from client‑wide defaults.
  • If you cannot upgrade immediately, modify the client’s request logic to reject any absolute blob‑upload URL whose host does not match the registry origin before sending authentication headers.
  • Implement network segmentation or firewall rules to restrict the library’s outbound connections to trusted registry hosts only, limiting the impact of an unauthorized registry.

Generated by OpenCVE AI on November 6, 2026 at 03:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-j63v-mwhm-56jx @sigstore/oci sends the registry Authorization header to a cross-host blob-upload Location
History
Type Values Removed Values Added
First Time appeared Sigstore
Sigstore sigstore
Vendors & Products Sigstore
Sigstore sigstore
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title @sigstore/oci sends the registry Authorization header to a cross-host blob-upload Location
Weaknesses CWE-522
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N'}

Weaknesses
  • CWE-201

    Insertion of Sensitive Information Into Sent Data

  • CWE-522

    Insufficiently Protected Credentials

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 5:13 PM
Reserved
Oct 28, 2026, 7:20 PM
Status
Deferred
Published
Oct 29, 2026, 5:18 PM
Modified
Oct 30, 2026, 7:39 PM
Severity
Moderate
Public date
Oct 29, 2026, 5:01 PM