Cyber Resilience

CVE-2026-20777

Memory Safety in Libbiosig Project Libbiosig 3.9.2

Public PoCMemory Safety
Published
03 March 2026
Modified
05 March 2026
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0051 41th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2026-20777 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Libbiosig Project Libbiosig. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A heap-based buffer overflow vulnerability, tracked as CVE-2026-20777 and published on 2026-03-03, affects the Nicolet WFT parsing functionality in The Biosig Project's libbiosig version 3.9.2 and the master branch at commit db9a9a63. This flaw, classified under CWE-122, carries a CVSS v3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Processing a specially crafted .wft file triggers the overflow, potentially leading to arbitrary code execution.

Remote attackers require no privileges or user interaction but must craft a file with high complexity to exploit this over a network. Successful exploitation grants high confidentiality, integrity, and availability impacts, enabling full arbitrary code execution in the context of the affected libbiosig process.

Mitigation details are available in the associated advisories from Talos Intelligence, referenced at https://talosintelligence.com/vulnerability_reports/TALOS-2026-2362 and https://www.talosintelligence.com/vulnerability_reports/TALOS-2026-2362.

EU & UK References

Vulnerability Data

A heap-based buffer overflow vulnerability exists in the Nicolet WFT parsing functionality of The Biosig Project libbiosig 3.9.2 and Master Branch (db9a9a63). A specially crafted .wft file can lead to arbitrary code execution. An attacker can provide a malicious file…

more

to trigger this vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-48005Same product: Libbiosig Project Libbiosig
CVE-2025-53853Same product: Libbiosig Project Libbiosig
CVE-2025-54462Same product: Libbiosig Project Libbiosig
CVE-2025-53557Same product: Libbiosig Project Libbiosig
CVE-2026-22891Same product: Libbiosig Project Libbiosig
CVE-2025-53511Same product: Libbiosig Project Libbiosig
CVE-2025-54484Same product: Libbiosig Project Libbiosig
CVE-2025-54482Same product: Libbiosig Project Libbiosig
CVE-2025-54483Same product: Libbiosig Project Libbiosig
CVE-2025-54487Same product: Libbiosig Project Libbiosig

Affected Assets

libbiosig project
libbiosig
3.9.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.

Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.

Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.

Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.

PR.PS-02 partial match
prevents

Timely patching removes known heap-overflow instances after they exist.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance can detect heap overflows before release.

prevents

Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.

prevents

Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.

prevents

Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.

prevents

Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.

none

Change management ensures controlled deployment of fixes for discovered heap-overflow vulnerabilities.

References