Arbitrary code execution via MFER null-byte overwrite
Published Aug 25, 2025 · Updated Nov 3, 2025
Stack-based buffer overflow in libbiosig 3.9.0 and master branch 35a819fa allows attackers to execute code via a crafted MFER file. The tag 3 character-code branch in biosig.c warns when the file-supplied len exceeds 16 but still writes a terminator to v[len] in a 17-byte stack buffer. Supplying a malicious MFER file is required; the resulting attacker-controlled out-of-bounds null write can corrupt the parsing process and enable arbitrary code execution.
Summary
What happened
Stack-based buffer overflow in libbiosig 3.9.0 and master branch 35a819fa allows attackers to execute code via a crafted MFER file. The tag 3 character-code branch in biosig.c warns when the file-supplied len exceeds 16 but still writes a terminator to v[len] in a 17-byte stack buffer. Supplying a malicious MFER file is required; the resulting attacker-controlled out-of-bounds null write can corrupt the parsing process and enable arbitrary code execution.
The record
- CVE
- CVE-2025-46411
- Published
- Aug 25, 2025
- Updated
- Nov 3, 2025
- Vendor
- The BioSig Project
- Product
- libbiosig
- Classifications
- CWE-121, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.9.0
- Affected versionversion=Master Branch (35a819fa)
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Talos MFER tag 3 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo