CVE-2026-48816 is a medium-severity security vulnerability in @sigstore/verify (npm), affecting versions = 3.1.0. It is fixed in 3.1.1.
sigstore-js derives a transparency-log timestamp from tlogEntries[].integratedTime and uses it to validate certificate validity windows and satisfy timestampThreshold. For bundle v0.2, a tlog entry can be inclusionProof-only (no signed inclusionPromise/set), and the inclusion proof path does not cryptographically bind integratedTime. As a result, an attacker who can supply an untrusted bundle can influence time-based verification decisions by choosing integratedTime. impact If a consumer accepts attacker-provided bundle v0.2 inputs and relies on tlog-derived timestamps for certificate validity checks, verification can be influenced by an unauthenticated timestamp value. This is a trust gap: integratedTime is treated as a trusted observer timestamp under inclusionProof-only mode even though only the signed inclusionPromise/set path binds it. affected code packages/verify/src/bundle/index.ts (adds a transparency-log timestamp whenever integratedTime != 0) packages/verify/src/timestamp/index.ts (converts integratedTime to a Date) packages/verify/src/verifier.ts (verifies timestamps before verifying tlog inclusion) packages/verify/src/tlog/index.ts + packages/verify/src/tlog/set.ts (only the inclusionPromise/set path binds integratedTime) proof of concept The attached poc.zip contains a self-contained harness that reproduces the behavior on the pinned commit and includes both a canonical test and a negative control. repro: 1) extract poc.zip into a fresh directory and run the make targets: 2) confirm canonical.log includes: 3) confirm control.log includes: suggested fix Only treat integratedTime as a trusted timestamp when it is cryptographically bound (for example, via a verified signed inclusionPromise/set). For inclusionProof-only entries, do not count integratedTime toward timestampThreshold, and do not use it for certificate validity decisions unless there is another signed time source (for example, an rfc3161 timestamp). poc.zip PRDESCRIPTION.md SUBMISSION.md
CVE-2026-48816 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (3.1.1). Upgrading removes the vulnerable code path.
npm
@sigstore/verify (= 3.1.0)@sigstore/verify → 3.1.1 (npm)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-48816 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-48816 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-48816 in your environment →Upgrade @sigstore/verify to 3.1.1 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-48816 is a medium-severity security vulnerability in @sigstore/verify (npm), affecting versions = 3.1.0. It is fixed in 3.1.1.
CVE-2026-48816 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
@sigstore/verify (npm) versions = 3.1.0 is affected.
Yes. CVE-2026-48816 is fixed in 3.1.1. Upgrade to this version or later.
Whether CVE-2026-48816 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade @sigstore/verify to 3.1.1 or later.