CVE-2026-48816
sigstore-js provides JavaScript libraries for interacting with Sigstore services. Prior to 3.1.1, @sigstore/verify derives a transparency-log timestamp from tlogEntries[].integratedTime for bundle v0.2 inclusionProof-only entries even though the inclusion proof path does not cryptographically bind integratedTime, allowing an attacker who can supply an untrusted bundle to influence certificate validity and timestampThreshold verification decisions. This issue is fixed in version 3.1.1.
- CVSS 3.1
- 6.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N - EPSS
- 0.1% chance of exploitation in the next 30 days; higher than 3% of CVEs (scores of 2026-10-25)
- CWE
- CWE-345
- Published
- Modified
- Record from
- the NVD, synced
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-xgjw-pm74-86q4 | npm | @sigstore/verify | >=3.1.0 <3.1.1 | 3.1.1 |
References
- https://github.com/sigstore/sigstore-js/commit/f074710a91ea9260a9ac2142345634579843a3cd
- https://github.com/sigstore/sigstore-js/pull/1659
- https://github.com/sigstore/sigstore-js/releases/tag/%40sigstore%2Fverify%403.1.1
- https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4
- https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4