CVE-2026-20911
Memory Safety in Libraw 0.22.0 … 0.22.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-20911 is a critical-severity Incorrect Calculation of Buffer Size (CWE-131) vulnerability in Libraw Libraw. Its CVSS base score is 9.8 (Critical).
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-20911, affects the HuffTable::initval functionality in LibRaw at commits 0b56545 and d20315b. This flaw, associated with CWE-131 (Incorrect Calculation of Buffer Size), can be triggered by processing a specially crafted malicious file, leading to a heap buffer overflow. The vulnerability carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating critical severity due to its potential for severe impact.
Any remote attacker can exploit this vulnerability without authentication or user interaction by supplying a malicious file to a vulnerable LibRaw instance, such as in image processing applications that rely on the library. Successful exploitation could result in arbitrary code execution, data corruption, or denial of service, with high impacts on confidentiality, integrity, and availability.
Mitigation details and additional technical analysis are provided in the Talos Intelligence advisory at https://talosintelligence.com/vulnerability_reports/TALOS-2026-2330. Security practitioners should review the report for patching guidance specific to affected LibRaw versions and consider input validation for file processing workflows.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-19622
Vulnerability Data
A heap-based buffer overflow vulnerability exists in the HuffTable::initval functionality of LibRaw Commit 0b56545 and Commit d20315b. A specially crafted malicious file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer security testing and code review can discover incorrect buffer-size computations before deployment.
Input validation directly enforces size checks before buffer copies.
Secure engineering principles directly require correct buffer-size arithmetic and bounds-checked allocation.
Memory-protection mechanisms limit the exploitability of an overflow that results from an incorrect size calculation.
Flaw-remediation processes that include vulnerability scanning or static analysis will surface buffer-size errors.
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.
Secure SDLC practices directly prevent buffer-size miscalculations via coding standards, reviews, and testing, while fixing this single weakness only partially fulfills the broader control.
Vulnerability identification processes such as code review or scanning detect classic buffer overflows before exploitation.
Routine patching replaces vulnerable code containing unchecked buffer copies with corrected versions.
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.
Secure coding standards directly require correct buffer-size calculations.
Security testing can detect buffer-size errors before release.
Secure development lifecycle mandates size-checking practices that reduce buffer-size miscalculations.
Application security requirements can specify buffer-size validation rules.
Secure architecture principles include safe memory-allocation guidelines.