Skip to main content
CVE-2025-53557VulnerabilityPublished Updated

CVE-2025-53557: The Biosig Project libbiosig · Heap-based Buffer Overflow

Affects The Biosig Project libbiosigSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
The Biosig Project libbiosigAffected
  • =3.9.0
Fixed in–

AI-suggested

Until official patches are released, European organizations should implement the following mitigations: 1) Restrict or disable processing of MFER files from untrusted or unauthenticated sources to prevent malicious input. 2) Employ input validation and sanitization mechanisms to detect and reject malformed or suspicious MFER files. 3) Use application-layer sandboxing or containerization to isolate the libbiosig-dependent components, limiting the impact of potential exploitation. 4) Monitor application logs and network traffic for unusual activity related to MFER file processing. 5) Apply runtime protections such as heap canaries, address space layout randomization (ASLR), and control flow integrity (CFI) to hinder exploitation. 6) Engage with The Biosig Project community for updates and patches, and plan prompt deployment once available. 7) Conduct code audits and penetration testing focused on MFER parsing functionality to identify additional weaknesses. 8) Educate staff about the risks of processing untrusted biometric data files.

Description

A heap-based buffer overflow vulnerability exists in the MFER parsing functionality of The Biosig Project libbiosig 3.9.0 and Master Branch (35a819fa). A specially crafted MFER file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger this vulnerability.

References

Community reviews

Loading reviews…