CVE-2025-53511: The Biosig Project libbiosig · Heap-based Buffer Overflow
Affects The Biosig Project libbiosigSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| The Biosig Project libbiosig | Affected
| Fixed in– |
AI-suggested
Until an official patch is released, European organizations should implement several specific mitigations: 1) Restrict and monitor all sources of MFER files, ensuring only trusted and validated inputs are processed by libbiosig-dependent applications. 2) Employ application-layer sandboxing or containerization to isolate processes that parse MFER files, limiting potential damage from exploitation. 3) Use runtime protections such as heap canaries, address space layout randomization (ASLR), and control flow integrity (CFI) where possible to reduce exploitation success. 4) Conduct code audits and implement additional input validation or bounds checking in custom wrappers around libbiosig if feasible. 5) Monitor network and host logs for unusual activity related to libbiosig usage or unexpected process behavior. 6) Coordinate with vendors and open-source maintainers to prioritize patch development and apply updates immediately upon release. 7) Educate relevant staff about the risks of processing untrusted biomedical data files and enforce strict operational security policies.
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.