Unauthorized artifact acceptance via dropped certificate OIDs
Published Jul 14, 2026 · Updated Jul 14, 2026
Improper certificate verification in Sigstore sigstore-js before 4.1.1 allows remote attackers to have unauthorized signing certificates accepted. The sigstore.verify() and createVerifier() policy path copies SAN and issuer settings but discards certificateOIDs before the verifier checks extension OID/value pairs. Exploitation requires an application to rely on certificateOIDs; a bundle still must satisfy every remaining verification check.
Summary
What happened
Improper certificate verification in Sigstore sigstore-js before 4.1.1 allows remote attackers to have unauthorized signing certificates accepted. The sigstore.verify() and createVerifier() policy path copies SAN and issuer settings but discards certificateOIDs before the verifier checks extension OID/value pairs. Exploitation requires an application to rely on certificateOIDs; a bundle still must satisfy every remaining verification check.
The record
- CVE
- CVE-2026-48815
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Sigstore
- Product
- sigstore-js
- Classifications
- CWE-347, T1553.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory policy-construction proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo