CVE-2026-48816: CWE-345: Insufficient Verification of Data Authenticity in sigstore sigstore-js
A vulnerability in sigstore-js prior to version 3.1.1 allows an attacker supplying an untrusted bundle to influence certificate validity and timestamp verification. This occurs because the library derives a transparency-log timestamp from a field that is not cryptographically bound in certain inclusion proof entries. The issue is fixed in version 3.1.1.
AI Analysis
Technical Summary
sigstore-js, a JavaScript library for interacting with Sigstore services, has an insufficient verification of data authenticity vulnerability (CWE-345) identified as CVE-2026-48816. Before version 3.1.1, the @sigstore/verify component derives a transparency-log timestamp from tlogEntries[].integratedTime for bundle v0.2 inclusionProof-only entries. However, the inclusion proof path does not cryptographically bind the integratedTime value, allowing an attacker who can supply an untrusted bundle to manipulate certificate validity and timestampThreshold verification decisions. This vulnerability has a CVSS 3.1 base score of 6.5 (medium severity) and is fixed in version 3.1.1.
Potential Impact
An attacker able to supply a crafted untrusted bundle can influence the verification process of certificates and timestamps by manipulating the transparency-log timestamp. This could lead to acceptance of invalid or malicious certificates, impacting the integrity of the verification process. There is no indication of confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade to sigstore-js version 3.1.1 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor advisory indicating the fix in 3.1.1. No other mitigations are specified.
CVE-2026-48816: CWE-345: Insufficient Verification of Data Authenticity in sigstore sigstore-js
Description
A vulnerability in sigstore-js prior to version 3.1.1 allows an attacker supplying an untrusted bundle to influence certificate validity and timestamp verification. This occurs because the library derives a transparency-log timestamp from a field that is not cryptographically bound in certain inclusion proof entries. The issue is fixed in version 3.1.1.
CVSS v3.1
Score 6.5medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
sigstore-js, a JavaScript library for interacting with Sigstore services, has an insufficient verification of data authenticity vulnerability (CWE-345) identified as CVE-2026-48816. Before version 3.1.1, the @sigstore/verify component derives a transparency-log timestamp from tlogEntries[].integratedTime for bundle v0.2 inclusionProof-only entries. However, the inclusion proof path does not cryptographically bind the integratedTime value, allowing an attacker who can supply an untrusted bundle to manipulate certificate validity and timestampThreshold verification decisions. This vulnerability has a CVSS 3.1 base score of 6.5 (medium severity) and is fixed in version 3.1.1.
Potential Impact
An attacker able to supply a crafted untrusted bundle can influence the verification process of certificates and timestamps by manipulating the transparency-log timestamp. This could lead to acceptance of invalid or malicious certificates, impacting the integrity of the verification process. There is no indication of confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade to sigstore-js version 3.1.1 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor advisory indicating the fix in 3.1.1. No other mitigations are specified.
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: 6a56a08568715ace432de59a
Added to database: 07/14/2026, 20:48:05 UTC
Last enriched: 07/14/2026, 21:08:05 UTC
Last updated: 07/14/2026, 21:08:05 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.