Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions 4.0.0 up to but not including 5.0.0 of biscuit-auth are affected. An attacker who holds a token can forge a third-party block request that alters the public key list in the symbol table, so a third-party authority signs a block that trusts a different keypair than intended. This lets the attacker use the token without a valid block from the intended authority. The source gives few details on exact conditions. Upgrade to biscuit-auth 5.0.0 or later; no workaround is listed.
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 |
|---|---|---|---|---|
| 3.0 | Low | 3.1 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0029, the 21st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:19 UTC First seen by agentprime
- 31 Oct 2026, 15:19 UTC Confirmed by OSV