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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 14:21 UTC First seen by agentprime
- 31 Oct 2026, 14:21 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-75rw-34q6-72cr
- OSV: GHSA-75rw-34q6-72cr
- github.com/biscuit-auth/biscuit/security/advisories/GHSA-75rw-34q6-72cr
- nvd.nist.gov/vuln/detail/CVE-2022-31053
- eprint.iacr.org/2020/1484
- github.com/advisories/GHSA-75rw-34q6-72cr
- github.com/biscuit-auth/biscuit
- pkg.go.dev/vuln/GO-2022-0564