How severe is CVE-2024-41949?

CVE-2024-41949 has a CVSS 3.x base score of 3.0, rated low severity. It is exploitable over network with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2024-41949 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2024-41949?

CVE-2024-41949 affects Biscuitsec Biscuit-auth. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-41949?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2024-41949 have an EU (EUVD) identifier?

Yes. CVE-2024-41949 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-2393.

When was CVE-2024-41949 published?

CVE-2024-41949 was published on 2024-08-01 and last updated on 2026-06-17.

CVE-2024-41949

CVE-2024-41949 is a low-severity vulnerability in Biscuitsec Biscuit-auth with a CVSS 3.x base score of 3.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-269.

Key facts

Severity: Low (CVSS 3.x base score 3.0)
EPSS exploit prediction: 0% (15th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-2393
Weakness: CWE-269
Affected product: Biscuitsec Biscuit-auth
Published: 2024-08-01
Last modified: 2026-06-17

Description

biscuit-rust is the Rust 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 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.

Frequently asked questions

What is CVE-2024-41949?: biscuit-rust is the Rust 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 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.
How severe is CVE-2024-41949?: CVE-2024-41949 has a CVSS 3.x base score of 3.0, rated low severity. It is exploitable over network with high attack complexity, requires high privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2024-41949 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-41949?: CVE-2024-41949 affects Biscuitsec Biscuit-auth. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-41949?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2024-41949 have an EU (EUVD) identifier?: Yes. CVE-2024-41949 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-2393.
When was CVE-2024-41949 published?: CVE-2024-41949 was published on 2024-08-01 and last updated on 2026-06-17.

References

https://github.com/biscuit-auth/biscuit-rust/security/advisories/GHSA-p9w4-585h-g3c7

Affected products (1)

cpe:2.3:a:biscuitsec:biscuit-auth:*:*:*:*:*:rust:*:*

More vulnerabilities in Biscuitsec Biscuit-auth

CVE-2022-31053 — Critical (CVSS 9.8): Biscuit is an authentication and authorization token for microservices architectures. The Biscuit specification version…

All CVEs affecting Biscuitsec Biscuit-auth →

Other CWE-269 (Improper Privilege Management) vulnerabilities

CVE-2026-31852 — Critical (CVSS 10.0): Jellyfin is an open-source media system. The code-quality.yml GitHub Actions workflow in jellyfin/jellyfin-ios is…
CVE-2025-20282 — Critical (CVSS 10.0): A vulnerability in an internal API of Cisco ISE and Cisco ISE-PIC could allow an unauthenticated, remote attacker to…
CVE-2025-0505 — Critical (CVSS 10.0): On Arista CloudVision systems (virtual or physical on-premise deployments), Zero Touch Provisioning can be used to gain…
CVE-2023-48418 — Critical (CVSS 10.0): In checkDebuggingDisallowed of DeviceVersionFragment.java, there is a possible way to access adb before SUW…
CVE-2023-48419 — Critical (CVSS 10.0): An attacker in the wifi vicinity of a target Google Home can spy on the victim, resulting in Elevation of Privilege
CVE-2023-31273 — Critical (CVSS 10.0): Protection mechanism failure in some Intel DCM software before version 5.2 may allow an unauthenticated user to…

Browse all CWE-269 (Improper Privilege Management) vulnerabilities →