Skip to main content
VulnerabilityPublished

CVE-2025-64736: The Biosig Project libbiosig · Out-of-bounds Read

Affects The Biosig Project libbiosigSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium.

Data as of 30 Oct 2026, 11:52 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Mar 2026

  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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
The Biosig ProjectlibbiosigAffected
  • =3.9.2
Fixed in–

AI-suggested

To mitigate CVE-2025-64736, organizations should: 1) Monitor The Biosig Project for official patches or updates addressing this vulnerability and apply them promptly once available. 2) Implement strict validation and sanitization of all .abf files before parsing, including file integrity checks and format verification to detect malformed or suspicious files. 3) Restrict the sources from which .abf files can be imported or processed, limiting to trusted and verified origins only. 4) Employ sandboxing or containerization for applications that parse .abf files to contain potential information leaks and limit memory exposure. 5) Enforce least privilege principles for users and processes handling biosignal data to reduce the risk of malicious file introduction and processing. 6) Conduct security awareness training for users to recognize and avoid opening untrusted or unexpected .abf files. 7) Monitor system logs and application behavior for anomalies during file parsing that could indicate exploitation attempts. These targeted measures go beyond generic advice by focusing on the specific attack vector and environment of libbiosig usage.

Description

An out-of-bounds read vulnerability exists in the ABF parsing functionality of The Biosig Project libbiosig 3.9.2 and Master Branch (5462afb0). A specially crafted .abf file can lead to an information leak. An attacker can provide a malicious file to trigger this vulnerability.

References

Community reviews

Loading reviews…