Biosig libbiosig 3.9.0 MFER Parser stack-based overflow

Summaryinfo

A vulnerability classified as critical has been found in Biosig libbiosig 3.9.0. This affects an unknown function of the component MFER Parser. Performing a manipulation results in stack-based overflow. This vulnerability is known as CVE-2025-46411. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, was found in Biosig libbiosig 3.9.0. This affects some unknown processing of the component MFER Parser. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A stack-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.

The advisory is shared at talosintelligence.com. This vulnerability is uniquely identified as CVE-2025-46411 since 07/23/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/02/2025).

The vulnerability scanner Nessus provides a plugin with the ID 260421 (Linux Distros Unpatched Vulnerability : CVE-2025-46411), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (260421). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Biosig

Name

• libbiosig

Version

• 3.9.0

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion