{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66044 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2025-66044 is a critical memory corruption vulnerability in The Biosig Project libbiosig, published on 11 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66044 and fix it if it is affected.\n\nWhat it is: CVE-2025-66044 is a critical memory corruption vulnerability in The Biosig Project libbiosig, published on 11 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66044 exists.\n\nAffected product: The Biosig Project libbiosig. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-66044/ (Markdown: https://insights.sbomify.com/CVE-2025-66044/index.md)","id":"CVE-2025-66044","markdown":"https://insights.sbomify.com/CVE-2025-66044/index.md","name":"CVE-2025-66044","record":{"aliases":["DEBIAN-CVE-2025-66044","GHSA-hh9q-f437-jrxh","UBUNTU-CVE-2025-66044"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Biosig signal library","requires_auth":"none","summary":"A stack-based buffer overflow in libbiosig allows arbitrary code execution via a specially crafted MFER file.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"libbiosig","vendor":"libbiosig_project"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"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 64","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in libbiosig","id":"CVE-2025-66044","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in libbiosig","id":"CVE-2025-66045"},"packages":[],"prev":{"headline":"Memory corruption in libbiosig","id":"CVE-2025-66043"},"products":["libbiosig"],"published":"2025-12-11","related":[{"cvss_score":9.8,"headline":"Memory corruption in libbiosig","id":"CVE-2026-22891","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":9.8,"headline":"Memory corruption in libbiosig","id":"CVE-2025-66043","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":9.8,"headline":"Memory corruption in libbiosig","id":"CVE-2025-66045","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":9.8,"headline":"Memory corruption in libbiosig","id":"CVE-2025-66046","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":9.8,"headline":"Memory corruption in libbiosig","id":"CVE-2025-66047","kev_date_added":null,"published":"2025-12-11"},{"cvss_score":9.8,"headline":"Memory corruption in libbiosig","id":"CVE-2025-66048","kev_date_added":null,"published":"2025-12-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-11","vendors":["The Biosig Project"]},"summary":"A stack-based buffer overflow in libbiosig allows arbitrary code execution via a specially crafted MFER file.","url":"https://insights.sbomify.com/CVE-2025-66044/"}