CVE-2026-48816
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…
Does this matter?
Lower severity and a low EPSS score (0.16%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 6.5 MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- EPSS
- 0.16% probability · 5th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-345
- Source
- security-advisories@github.com
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
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.