CVE-2026-48816mediumCWE-345

CVE-2026-48816: medium-severity vulnerability in sigstore-js

sigstore-js: Insufficient Verification of Data Authenticity

Published · Updated

Follow this CVE+ Monitor sigstore-js+ Monitor @sigstore/verify

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

13Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 6.5epss 0.1%
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/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Affected products
sigstore · sigstore-js
Related CVEs — sigstore-js

In the same product, most dangerous first.

CVE-2026-59891CRITICALCredential confusion in  @sigstore/oci  can leak registry credentials to an attacker-controlled registryEPSS 0.5%CVE-2026-118763HIGH@sigstore/oci sends the registry Authorization header to a cross-host blob-upload LocationEPSS 0.3%CVE-2026-48758MEDIUMsigstore-js: DSSE payloadType type-binding failureEPSS 0.2%CVE-2026-48815HIGHsigstore-js: `certificateOIDs` verification constraints are silently dropped and never enforcedEPSS 0.2%