biscuit-java vulnerable to public key confusion in third party block

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N · score source

EPSS

• CVE-2024-41948: 0.28% estimated exploitation activity in the next 30 days; percentile 20.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Tokens with third-party blocks containing trusted annotations generated through a third party block request. Due to implementation issues in biscuit-java, third party block support in published versions is inoperating. Nevertheless, to synchronize with other implementations, we publish this advisory and the related fix. Description 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: the public key of the previous block (used in the signature) the public keys part of the token symbol table (for public key interning in datalog expressions) A third-part block request forged by a malicious user can trick the third-party authority into generating datalog trusting the wrong keypair. Consider the following example (nominal case) Authority A emits the following token: check if thirdparty("b") trusting…

Published by the source

31 Jul 2024, 18:48 UTC

Last modified by the source

18 Nov 2024, 16:26 UTC

Source last checked

26 Oct 2026, 16:31 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5hcj-rwm6-xmw4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-41948

Advisory: biscuit-java vulnerable to public key confusion in third party block
IDs: CVE-2024-41948, GHSA-5hcj-rwm6-xmw4
Record: https://patchnext.com/advisories/cve-2024-41948 (revision 1, source checked 26 Oct 2026, 16:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.biscuitsec:biscuit 4.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.biscuitsec:biscuit: affected >= 3.0.0, < 4.0.0; fixed in 4.0.0

## Suggested inspection (read-only)
- Maven org.biscuitsec:biscuit: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.biscuitsec:biscuit.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5hcj-rwm6-xmw4 (GitHub-reviewed advisory GHSA-5hcj-rwm6-xmw4 lists affected ranges: Maven org.biscuitsec:biscuit >=3.0.0 <4.0.0)

Commands are suggestions: review each one before running it.