CVE-2026-48815: CWE-347: Improper Verification of Cryptographic Signature in sigstore sigstore-js
sigstore-js versions prior to 4.1.1 have a vulnerability where the certificateOIDs option in the sigstore.verify() function is accepted by the API but ignored during verification. This means that required certificate extension OIDs are not checked, allowing applications that rely on this option to restrict signing certificates to potentially accept unauthorized certificates. The issue is fixed in version 4.1.1.
AI Analysis
Technical Summary
The vulnerability in sigstore-js (CVE-2026-48815) involves improper verification of cryptographic signatures due to the certificateOIDs option being discarded before verification in versions prior to 4.1.1. Applications using this option to restrict which certificates may sign artifacts can be bypassed, as the required certificate extension OIDs are never enforced. This flaw is classified under CWE-347 (Improper Verification of Cryptographic Signature). The issue is resolved in sigstore-js version 4.1.1.
Potential Impact
Applications relying on the certificateOIDs option in sigstore-js to restrict signing certificates may accept unauthorized certificates, potentially allowing attackers to sign artifacts without proper authorization. This undermines the integrity assurance provided by signature verification but does not affect confidentiality or availability directly. There are no known exploits in the wild at this time.
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 other mitigations are indicated.
CVE-2026-48815: CWE-347: Improper Verification of Cryptographic Signature in sigstore sigstore-js
Description
sigstore-js versions prior to 4.1.1 have a vulnerability where the certificateOIDs option in the sigstore.verify() function is accepted by the API but ignored during verification. This means that required certificate extension OIDs are not checked, allowing applications that rely on this option to restrict signing certificates to potentially 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 (CVE-2026-48815) involves improper verification of cryptographic signatures due to the certificateOIDs option being discarded before verification in versions prior to 4.1.1. Applications using this option to restrict which certificates may sign artifacts can be bypassed, as the required certificate extension OIDs are never enforced. This flaw is classified under CWE-347 (Improper Verification of Cryptographic Signature). The issue is resolved in sigstore-js version 4.1.1.
Potential Impact
Applications relying on the certificateOIDs option in sigstore-js to restrict signing certificates may accept unauthorized certificates, potentially allowing attackers to sign artifacts without proper authorization. This undermines the integrity assurance provided by signature verification but does not affect confidentiality or availability directly. There are no known exploits in the wild at this time.
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 other 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/21/2026, 22:47:31 UTC
Last updated: 08/28/2026, 10:52:08 UTC
Views: 87
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.