[From nobody Sun Apr 26 10:23:05 2026
Received: (at submit) by bugs.debian.org; 13 Dec 2025 13:47:47 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-8.5 required=4.0 tests=BAYES_00, FOURLA,
 FROMDEVELOPER, 
 KHOP_HELO_FCRDNS,RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,
 RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,
 RDNS_DYNAMIC,SPF_HELO_NONE,SPF_NONE,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 41; hammy, 149; neutral, 46; spammy,
 1. spammytokens:0.942-+--H*r:bugs.debian.org
 hammytokens:0.000-+--H*F:U*carnil, 0.000-+--XDebbugsCc,
 0.000-+--X-Debbugs-Cc, 0.000-+--forky, 0.000-+--H*Ad:N*Bug
Return-path: &lt;carnil@debian.org&gt;
Received: from c-82-192-244-13.customer.ggaweb.ch ([82.192.244.13]:38366
 helo=eldamar.lan) by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from &lt;carnil@debian.org&gt;) id 1vUPyL-0000ut-2k
 for submit@bugs.debian.org; Sat, 13 Dec 2025 13:47:47 +0000
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: biosig: CVE-2025-66047 CVE-2025-66045 CVE-2025-66044 CVE-2025-66048
 CVE-2025-66043 CVE-2025-66046
Message-ID: &lt;176563366483.240788.11060829125548846227.reportbug@eldamar.lan&gt;
X-Mailer: reportbug 13.2.0
Date: Sat, 13 Dec 2025 14:47:44 +0100
Delivered-To: submit@bugs.debian.org

Source: biosig
Version: 3.9.0-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team &lt;team@security.debian.org&gt;

Hi,

The following vulnerabilities were published for biosig.

Filling this as RC level as it should be fixed for forky.

CVE-2025-66047[0]:
| 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


CVE-2025-66045[1]:
| 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 65


CVE-2025-66044[2]:
| 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 64


CVE-2025-66048[3]:
| 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 133


CVE-2025-66043[4]:
| 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 3


CVE-2025-66046[5]:
| 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 67


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2025-66047
    https://www.cve.org/CVERecord?id=CVE-2025-66047
[1] https://security-tracker.debian.org/tracker/CVE-2025-66045
    https://www.cve.org/CVERecord?id=CVE-2025-66045
[2] https://security-tracker.debian.org/tracker/CVE-2025-66044
    https://www.cve.org/CVERecord?id=CVE-2025-66044
[3] https://security-tracker.debian.org/tracker/CVE-2025-66048
    https://www.cve.org/CVERecord?id=CVE-2025-66048
[4] https://security-tracker.debian.org/tracker/CVE-2025-66043
    https://www.cve.org/CVERecord?id=CVE-2025-66043
[5] https://security-tracker.debian.org/tracker/CVE-2025-66046
    https://www.cve.org/CVERecord?id=CVE-2025-66046
[6] https://sourceforge.net/p/biosig/mailman/message/59271419/
[7] https://talosintelligence.com/vulnerability_reports/TALOS-2025-2296

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]