Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-31053: Biscuit is an authentication and authorization token for microservices architectures

60
This week
CRITICAL 9.8REMOTEUPGRADEUPGRADEDOWNGRADE

CVE-2022-31053 is a critical-severity flaw (CVSS 9.8) affecting biscuit-auth, biscuit-go, biscuit-haskell. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Biscuit is an authentication and authorization token for microservices architectures. The Biscuit specification version 1 contains a vulnerable algorithm that allows malicious actors to forge valid Γ-signatures. Such an attack would allow an attacker to create a token with any access level. The version 2 of the specification mandates a different algorithm than gamma signatures and as such is not affected by this vulnerability. The Biscuit impleme

Why this priority

  • Critical severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.0% (top 37%)
CISA exploited listNo
WeaknessCWE-347
Published2022-06-13
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: biscuitsec · clever-cloud

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

biscuitsec biscuit-auth UPGRADE
Affected: >= 1.0.0 and <= 1.1.0
Fixed in: newer than 1.1.0
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy biscuit-auth || rpm -q biscuit-auth || biscuit-auth --version
2. UPGRADE to newer than 1.1.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade biscuit-auth
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade biscuit-auth
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison biscuit-auth sudo apt install biscuit-auth=<VERSION_BEFORE_1.0.0> sudo apt-mark hold biscuit-auth
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list biscuit-auth sudo dnf downgrade biscuit-auth-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add biscuit-auth
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
biscuitsec biscuit-go UPGRADE
Affected: < 2.0.0
Fixed in: 2.0.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy biscuit-go || rpm -q biscuit-go || biscuit-go --version
2. UPGRADE to 2.0.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade biscuit-go
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade biscuit-go
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
biscuitsec biscuit-haskell DOWNGRADE
Affected: 0.1.1.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 0.1.1.0
1. Check installed version
apt-cache policy biscuit-haskell || rpm -q biscuit-haskell || biscuit-haskell --version
2. No fixed release: DOWNGRADE to a release before 0.1.1.0 (Debian / Ubuntu)
apt-cache madison biscuit-haskell sudo apt install biscuit-haskell=<VERSION_BEFORE_0.1.1.0> sudo apt-mark hold biscuit-haskell
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list biscuit-haskell sudo dnf downgrade biscuit-haskell-<VERSION_BEFORE_0.1.1.0> sudo dnf versionlock add biscuit-haskell
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
clever-cloud biscuit-java UPGRADE
Affected: < 2.0.0
Fixed in: 2.0.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy biscuit-java || rpm -q biscuit-java || biscuit-java --version
2. UPGRADE to 2.0.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade biscuit-java
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade biscuit-java
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-31053?

biscuit-auth: upgrade to newer than 1.1.0; biscuit-go: upgrade to 2.0.0; biscuit-haskell: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-31053 being exploited?

CVE-2022-31053 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-31053 affect?

CVE-2022-31053 affects biscuit-auth, biscuit-go, biscuit-haskell. Severity is critical (CVSS 9.8). Biscuit is an authentication and authorization token for microservices architectures. The Biscuit specification version 1 contains a vulnerable algorithm that allows malicious actors to forge valid Γ-signatures. Such an attack would allow a

How urgent is CVE-2022-31053?

Priority 60/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.