Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-48816 medium CVSS 6.5

Vulnerability in @sigstore/verify (CVE-2026-48816)

Summary

Vulnerability in @sigstore/verify (CVE-2026-48816). Data can be tampered with by attackers. Exploitable via timestampThreshold. Mitigation: upgrade to 3.1.1 or later.

Original description

The description as published by the source.

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. ext…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-48816 has been found in @sigstore/verify.
Attackers can target a specific entry point like timestampThreshold over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade @sigstore/verify to 3.1.1 or later.
If unsure, ask your IT team or search "@sigstore/verify CVE-2026-48816" on the vendor's site.

CVE-2026-48816 (@sigstore/verify) — CWE-345 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: timestampThreshold / integratedTime / Date / poc.zip
Patched: 3.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-345) exists in @sigstore/verify. Attackers reach the vulnerable code path via timestampThreshold.

📍 Affected scope

Check the vendor advisory for the affected versions of @sigstore/verify. Attack surface: timestampThreshold / integratedTime / Date / poc.zip.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 3.1.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@sigstore/verify' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@sigstore/verify' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @sigstore/verify を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @sigstore/verify to 3.1.1

    ステージング環境で 3.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @sigstore/verify
[{"type":"SEMVER","events":[{"introduced":"3.1.0"},{"fixed":"3.1.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details