Zero Radar
← feed
HighVulnerabilityCVE-2026-118763updated 30 Oct 2026, 23:00 UTC

Sigstore OCI library can send registry login details to a different server

When this library uploads a file to a container registry, it can accidentally send the login token or password to another website if the registry points it there. Someone running a hostile or hacked registry could collect those credentials.

Fixed in 0.7.2 · out Official, 2 sources
SeverityHighCVSS 7.4 of 10
Being exploited?UnclearNo reports either way yet
Fix available?Yes0.7.2 · since 30 Oct 2026
How sure is this?Official, 2 sourcesBacked by an official source

How the attack works simplified

  1. 1Hostile registryControls registry responses to the client
  2. 2Upload redirectReturns absolute Location on another host
  3. 3Client PUTs blobSends blob with registry Authorization header
  4. 4Credentials capturedAttacker host receives the token
  5. ResultAttacker obtains registry credentials

What happened

In @sigstore/oci up to 0.7.1, the registry Authorization header is attached to all requests, and uploadBlob() PUTs blobs to any absolute Location URL returned by the registry without checking that its host or scheme matches the registry, leaking bearer tokens, Basic credentials, or custom auth headers cross-host.

Why it is dangerous: A malicious or compromised registry can capture the registry bearer token, Basic username/password, or custom authentication headers of anyone pushing an artifact with attachArtifactToImage(), potentially giving the attacker access to the user's registry account.

Are you affected?

You are affected if you use @sigstore/oci version 0.7.1 or earlier to push signed artifacts or attestations to an OCI registry with attachArtifactToImage().

Package / productAffected versionsFixed in
@sigstore/oci · npm<= 0.7.10.7.2

What to do

  1. Update @sigstore/oci to version 0.7.2 or later
  2. Rotate registry tokens or passwords used with affected versions if you pushed artifacts through a registry you do not fully trust

Timeline

  1. 29 Oct 2026, 17:18 UTC
    Publicly disclosed
  2. 29 Oct 2026, 17:18 UTC
    Reported by NVD · NVD
  3. 29 Oct 2026, 17:20 UTC
    Picked up by Zero Radar
  4. 30 Oct 2026, 23:00 UTC
    GitHub Advisory reported on it · GitHub Advisory
  5. 30 Oct 2026, 23:00 UTC
    Fixed version published: @sigstore/oci 0.7.2 · GitHub Advisory

Sources 2 reports, oldest first

Official vendor, government CERT or advisory database

Technical details

ID
CVE-2026-118763 · GHSA-j63v-mwhm-56jx
CVSS
7.4 / 10
Disclosed
29 Oct 2026, 17:18 UTC
On Zero Radar
29 Oct 2026, 17:20 UTC (2 min after disclosure)
Last change
30 Oct 2026, 23:00 UTC

The plain-language parts and the attack diagram were written by an AI model (anthropic/claude-haiku-5.5) from the sources above. Facts like versions, exploitation and dates come from the sources themselves. How Zero Radar works

Sigstore OCI library can send registry login details to a different server · Zero Radar