Skip to main content
VulnerabilityPublished

CVE-2024-41949: Biscuit haskell · Public key confusion in third-party blocks

Affects biscuit-haskellSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 0.4.0.0 soon.

Data as of 13 Nov 2026, 18:41 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Patch
Available – fixed in 0.4.0.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade biscuit-haskell to 0.4.0.0.

Affected software

ProductAffectedFixed in
Hackagebiscuit-haskellAffected
  • >=0.3.0.0 <0.4.0.0
Fixed in
  • 0.4.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade biscuit-haskell to version 0.4.0.0 or later, where this vulnerability is fixed. The patch is available and should be applied to prevent exploitation of this public key confusion issue.

Description

A vulnerability in biscuit-haskell versions 0.3.0.0 up to but not including 0.4.0.0 allows a malicious user to forge third-party block requests. This can cause the third-party authority to generate datalog trusting an incorrect keypair due to public key confusion in third-party blocks. The issue is fixed in version 0.4.0.0.

References

Community reviews

Loading reviews…