CVE-2024-41948: biscuit-java is the java implementation of Biscuit, an authentication and authorization token for microservice

Routine

LOW 3.0UPGRADE

CVE-2024-41948 is a low-severity flaw (CVSS 3.0) affecting biscuit-java. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

biscuit-java is the java implementation of Biscuit, an authentication and authorization token for microservices architectures. Third-party blocks can be generated without transferring the whole token to the third-party authority. Instead, a ThirdPartyBlock request can be sent, providing only the necessary info to generate a third-party block and to sign it, which includes the public key of the previous block (used in the signature) and the public

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.0 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	High
User interaction	None
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-1259
Published	2024-08-01
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: biscuitsec

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

Am I affected?

Timeline

2024-08-01 22:15 UTCPublished CVE record published
2026-06-17 07:48 UTCUpdated Record last modified

biscuitsec biscuit-java UPGRADE

Affected: >= 3.0.0 and < 4.0.0

Fixed in: 4.0.0

Safe to downgrade to: a release before 3.0.0

1. Check installed version

apt-cache policy biscuit-java || rpm -q biscuit-java || biscuit-java --version

2. UPGRADE to 4.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.

3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison biscuit-java sudo apt install biscuit-java=<VERSION_BEFORE_3.0.0> sudo apt-mark hold biscuit-java

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list biscuit-java sudo dnf downgrade biscuit-java-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add biscuit-java

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.

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-2024-41948?

biscuit-java: upgrade to 4.0.0. Exact commands for each OS are on this page.

Is CVE-2024-41948 being exploited?

CVE-2024-41948 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-2024-41948 affect?

CVE-2024-41948 affects biscuit-java. Severity is low (CVSS 3.0). biscuit-java is the java implementation of Biscuit, an authentication and authorization token for microservices architectures. Third-party blocks can be generated without transferring the whole token to the third-party authority. Instead, a

How urgent is CVE-2024-41948?

Priority 16/100. No elevated risk signals yet.

Software pages

Java vulnerabilities

References

← Back to latest CVEs