CVE-2026-48815: CWE-347: Improper Verification of Cryptographic Signature in sigstore sigstore-js
CVE-2026-48815 affects sigstore-js, a JavaScript library for interacting with Sigstore services. Before version 4.1.1, the certificateOIDs option in the sigstore.verify() function was accepted by the public API but ignored during verification. This flaw allowed applications relying on certificateOIDs to restrict signing certificates to inadvertently accept unauthorized certificates. The issue is fixed in version 4.1.1.
AI Analysis
Technical Summary
The vulnerability in sigstore-js involves improper verification of cryptographic signatures due to the certificateOIDs option being discarded before verification. This means that required certificate extension Object Identifiers (OIDs) are never checked, undermining the intended restriction on which certificates may sign artifacts. This can lead to acceptance of unauthorized signatures. The problem is resolved in sigstore-js version 4.1.1.
Potential Impact
Applications using sigstore-js versions prior to 4.1.1 that rely on the certificateOIDs option to restrict signing certificates may accept signatures from unauthorized certificates. This compromises the integrity of the signature verification process, potentially allowing malicious artifacts to be accepted as valid. There is no indication of confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade sigstore-js to version 4.1.1 or later, where the certificateOIDs option is properly enforced during signature verification. Patch status is confirmed by the vendor stating the issue is fixed in 4.1.1. No alternative mitigations are indicated.
CVE-2026-48815: CWE-347: Improper Verification of Cryptographic Signature in sigstore sigstore-js
Description
CVE-2026-48815 affects sigstore-js, a JavaScript library for interacting with Sigstore services. Before version 4.1.1, the certificateOIDs option in the sigstore.verify() function was accepted by the public API but ignored during verification. This flaw allowed applications relying on certificateOIDs to restrict signing certificates to inadvertently accept unauthorized certificates. The issue is fixed in version 4.1.1.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in sigstore-js involves improper verification of cryptographic signatures due to the certificateOIDs option being discarded before verification. This means that required certificate extension Object Identifiers (OIDs) are never checked, undermining the intended restriction on which certificates may sign artifacts. This can lead to acceptance of unauthorized signatures. The problem is resolved in sigstore-js version 4.1.1.
Potential Impact
Applications using sigstore-js versions prior to 4.1.1 that rely on the certificateOIDs option to restrict signing certificates may accept signatures from unauthorized certificates. This compromises the integrity of the signature verification process, potentially allowing malicious artifacts to be accepted as valid. There is no indication of confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade sigstore-js to version 4.1.1 or later, where the certificateOIDs option is properly enforced during signature verification. Patch status is confirmed by the vendor stating the issue is fixed in 4.1.1. No alternative mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-22T20:57:10.976Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a56a08568715ace432de594
Added to database: 07/14/2026, 20:48:05 UTC
Last enriched: 07/14/2026, 21:02:37 UTC
Last updated: 07/14/2026, 21:07:26 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.