Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-66047: CWE-121: Stack-based Buffer Overflow in The Biosig Project libbiosig

0
Critical
VulnerabilityCVE-2025-66047cvecve-2025-66047cwe-121
Published: Thu Dec 11 2025 (12/11/2025, 16:43:57 UTC)
Source: CVE Database V5
Vendor/Project: The Biosig Project
Product: libbiosig

Description

Several stack-based buffer overflow vulnerabilities exists in the MFER parsing functionality of The Biosig Project libbiosig 3.9.1. A specially crafted MFER file can lead to arbitrary code execution. An attacker can provide a malicious file to trigger these vulnerabilities.When Tag is 131

AI-Powered Analysis

AILast updated: 12/11/2025, 17:24:08 UTC

Technical Analysis

CVE-2025-66047 is a critical security vulnerability identified in version 3.9.1 of libbiosig, an open-source library widely used for processing biosignal data such as EEG, ECG, and other physiological signals. The vulnerability is a stack-based buffer overflow (CWE-121) located in the MFER (Medical File Exchange Record) parsing functionality, specifically triggered when processing Tag 131 within an MFER file. This flaw allows an attacker to craft a malicious MFER file that, when parsed by libbiosig, causes a buffer overflow on the stack, potentially overwriting the return address or other control data. This can lead to arbitrary code execution in the context of the vulnerable application without requiring any privileges or user interaction, making it remotely exploitable over networked systems that accept MFER files. The CVSS v3.1 base score of 9.8 reflects the high severity, with metrics indicating network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and full impact on confidentiality, integrity, and availability (C:H/I:H/A:H). Although no public exploits have been reported yet, the nature of the vulnerability and the widespread use of libbiosig in medical and research environments make it a critical risk. The lack of available patches at the time of disclosure increases the urgency for mitigations. The vulnerability was reserved on 2025-11-21 and published on 2025-12-11, indicating recent discovery and disclosure.

Potential Impact

The impact of CVE-2025-66047 on European organizations is significant, particularly for those in healthcare, biomedical research, and industries relying on biosignal processing. Successful exploitation can lead to full system compromise, allowing attackers to execute arbitrary code, steal sensitive patient or research data, disrupt medical devices or research operations, and potentially cause harm to patients if medical devices are involved. The confidentiality of sensitive health data could be breached, integrity of biosignal data corrupted, and availability of critical systems disrupted. Given the critical nature of healthcare infrastructure in Europe and stringent data protection regulations like GDPR, such a breach could result in severe regulatory penalties, reputational damage, and operational downtime. Organizations using libbiosig in medical devices, research labs, or clinical environments are particularly vulnerable. The absence of known exploits currently provides a window for proactive defense, but the ease of exploitation and high severity score indicate a high risk of imminent attacks once exploit code becomes available.

Mitigation Recommendations

To mitigate CVE-2025-66047, European organizations should immediately identify all systems and applications using libbiosig version 3.9.1, especially those processing MFER files. Since no official patch is available at disclosure, organizations should implement strict input validation and sanitization for MFER files, including rejecting or sandboxing files containing Tag 131 until a patch is released. Employ runtime protections such as stack canaries, address space layout randomization (ASLR), and control flow integrity (CFI) to reduce exploitation risk. Monitor network traffic and file uploads for suspicious MFER files and implement intrusion detection signatures targeting malformed MFER parsing attempts. Coordinate with vendors and open-source maintainers for timely patch releases and apply updates immediately upon availability. Additionally, conduct code audits and penetration testing focused on biosignal processing components. For critical medical devices, consider isolating affected systems from external networks and applying strict access controls. Maintain up-to-date backups and incident response plans tailored to biosignal processing environments.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
talos
Date Reserved
2025-11-21T10:23:41.665Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693afaa97d4c6f31f7bae1e8

Added to database: 12/11/2025, 5:08:57 PM

Last enriched: 12/11/2025, 5:24:08 PM

Last updated: 12/11/2025, 10:45:23 PM

Views: 11

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats