Description
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.
References5
- github.com/sigstore/sigstore-js/commit/f074710a91ea9260a9ac2142…
- github.com/sigstore/sigstore-js/pull/1659
- github.com/sigstore/sigstore-js/releases/tag/%40sigstore%2Fveri…
- github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-p…
- github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-p…
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N - EPSS — exploit probability
- 0% percentile: 4 · as of 15 November 2026
- CWE
- CWE-345
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.