# CVE-2025-64736: Information disclosure in libbiosig

> An out-of-bounds read in libbiosig allows attackers to leak information via a crafted ABF file, affecting applications using this library.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Mar 2026
- **Updated:** 3 Mar 2026
- **Also known as:** DEBIAN-CVE-2025-64736, GHSA-p3cr-g43c-99g8, UBUNTU-CVE-2025-64736

## What is CVE-2025-64736?

CVE-2025-64736 is a medium-severity vulnerability in The Biosig Project libbiosig, published on 3 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-64736?

It affects 1 product.


Products: Libbiosig Project Libbiosig.

## How do I fix CVE-2025-64736?

Apply the vendor's patch.

## Is CVE-2025-64736 being exploited?

There is no known exploitation of CVE-2025-64736 in the wild and no public exploit code.

## Other vulnerabilities in The Biosig Project libbiosig

- [CVE-2026-22891](https://insights.sbomify.com/CVE-2026-22891/): Memory corruption in libbiosig (critical 9.8)
- [CVE-2025-66043](https://insights.sbomify.com/CVE-2025-66043/): Memory corruption in libbiosig (critical 9.8)
- [CVE-2025-66044](https://insights.sbomify.com/CVE-2025-66044/): Memory corruption in libbiosig (critical 9.8)
- [CVE-2025-66045](https://insights.sbomify.com/CVE-2025-66045/): Memory corruption in libbiosig (critical 9.8)
- [CVE-2025-66046](https://insights.sbomify.com/CVE-2025-66046/): Memory corruption in libbiosig (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64736 and fix it if it is affected.

What it is: CVE-2025-64736 is a medium-severity vulnerability in The Biosig Project libbiosig, published on 3 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-64736 in the wild and no public exploit code.

Affected product: The Biosig Project libbiosig. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64736/ (Markdown: https://insights.sbomify.com/CVE-2025-64736/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64736
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64736
- OSV: https://osv.dev/vulnerability/CVE-2025-64736

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64736/
Summaries are generated and may contain mistakes; the official description above is the record.