Advisory record · GHSA-cq38-jh5f-37mq

sigstore-go has an unbounded loop over untrusted input can lead to endless data attack

CVSS 3.1 LowEPSS 0.0047 · 41st percentile

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

PackageEcosystemAffectedFixed in
github.com/sigstore/sigstore-goGo<0.6.10.6.1
Identifiers
GHSA-cq38-jh5f-37mq · CVE-2024-45395 · GO-2024-3116
Weakness (CWE)
CWE-835
Published
4 Sept 2024
Updated
10 Sept 2026

Machine-written summary

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

Versions of github.com/sigstore/sigstore-go before 0.6.1 are vulnerable to a denial of service. An attacker who can supply a maliciously crafted Sigstore Bundle to a verifier can make verification consume excessive CPU by including large numbers of transparency log entries, RFC 3161 timestamps, or attestation subjects. Upgrade to version 0.6.1 or later, which limits how many of these items a bundle may contain.

Written 2 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
3.1 Low 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0047, the 41st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 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.