Advisory record · GHSA-75rw-34q6-72cr

Signature forgery in Biscuit

CVSS 9.8 CriticalCriticalEPSS 0.010 · 64th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 17 Jun 2022, 00:38 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
biscuit-authcrates.io>=1.0.0, <2.0.02.0.0
github.com/biscuit-auth/biscuit-goGo<2.0.02.0.0
com.clever-cloud:biscuit-javaMaven<2.0.02.0.0
Identifiers
GHSA-75rw-34q6-72cr · CVE-2022-31053 · GO-2022-0564 · HSEC-2023-0002
Weakness (CWE)
CWE-347
Published
17 Jun 2022
Updated
4 Feb 2026

Machine-written summary

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

Biscuit (biscuit-auth on crates.io versions 1.0.0 to before 2.0.0, biscuit-go before 2.0.0, and biscuit-java before 2.0.0) is vulnerable to signature forgery because the Γ-signature algorithm used in Biscuit specification version 1 can be broken. An attacker could forge a token granting any access level, and the source gives no indication of active exploitation. Upgrade to version 2.0.0 of the affected package; the source states that there is no workaround and that Biscuit v1 tokens should be migrated to v2.

Written 3 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
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.010, the 64th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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