Advisory record · GHSA-hhfg-fwrw-87w7

sigstore has insufficient validation of integration timestamp during verification

CVSS 2.7 LowEPSS 0.0025 · 16th percentile

Published by the GitHub Advisory Database at 11 Dec 2024, 18:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
sigstorePyPI>=2.0.0, <3.6.03.6.0
Identifiers
GHSA-hhfg-fwrw-87w7 · CVE-2024-55655 · PYSEC-2026-1923
Weakness (CWE)
CWE-20 · CWE-325
Published
11 Dec 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of sigstore from 2.0.0 up to but not including 3.6.0 insufficiently validate the integration timestamp in v2 and v3 bundles during verification. The timestamp is only checked when a source of signed time, such as an inclusion promise, is present; otherwise it is trusted. An attacker who can modify a bundle could alter the timestamp, but the source reports the impact as low, mainly causing denial of service, since other checks still reject forged signatures. Upgrade to sigstore 3.6.0 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.7 Low 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0025, the 16th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:35 UTC First seen by agentprime
  2. 31 Oct 2026, 14:35 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.