CVE-2026-118763
Last modified
CVE-2026-118763 is a high-severity vulnerability rated 7.4/10 on the CVSS scale. 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. EPSS estimates a 0.30% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| sigstore | sigstore-js | < 0.7.2 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-118763?
How severe is CVE-2026-118763?
How do I fix CVE-2026-118763?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-118758Kubeflow Pipelines enables users to build and deploy portabl…7.5
- CVE-2026-118759Kubeflow Pipelines enables users to build and deploy portabl…7.5
- CVE-2026-11876In zenml-io/zenml version 0.94.2, the `GET /api/v1/stack-dep…5
- CVE-2026-118760Kubeflow Pipelines enables users to build and deploy portabl…6.5
- CVE-2026-118761Kubeflow Pipelines enables users to build and deploy portabl…7.5
- CVE-2026-118762Monkeytype is a minimalistic and customizable typing test. P…9.3
- CVE-2026-118764minimatch is a minimal matching utility for converting glob …6.9
- CVE-2026-118765Botan is a C++ cryptography library. From 3.7.0 until 3.13.0…7.3
- CVE-2026-118766Botan is a C++ cryptography library. Prior to 3.13.0, Botan'…6.1
- CVE-2026-118767Botan is a C++ cryptography library. From 1.11.22 until 3.13…4.8
- CVE-2026-118768Botan is a C++ cryptography library. From 1.11.34 until 3.13…5.9
- CVE-2026-118769Botan is a C++ cryptography library. From 2.1.0 until 3.13.0…9.2
Are you affected by CVE-2026-118763?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
