CVE-2026-22791
Opencryptoki Project Opencryptoki 3.25.0 … 3.26.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:HSummary
CVE-2026-22791 is a medium-severity Incorrect Calculation of Buffer Size (CWE-131) vulnerability in Opencryptoki Project Opencryptoki. Its CVSS base score is 6.6 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 15th 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 SI-10 (Information Input Validation) and SI-16 (Memory Protection) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-2415
Vulnerability Data
openCryptoki is a PKCS#11 library and tools for Linux and AIX. In 3.25.0 and 3.26.0, there is a heap buffer overflow vulnerability in the CKM_ECDH_AES_KEY_WRAP implementation allows an attacker with local access to cause out-of-bounds writes in the host process…
more
by supplying a compressed EC public key and invoking C_WrapKey. This can lead to heap corruption, or denial-of-service.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Local heap buffer overflow enables exploitation for privilege escalation via memory corruption.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces validation of EC public-key input length and format before C_WrapKey processing, preventing the incorrect buffer-size calculation (CWE-131) that triggers the heap overflow.
Applies memory-protection mechanisms that block or contain out-of-bounds writes in the PKCS#11 host process, mitigating heap corruption even if malformed compressed keys reach the vulnerable CKM_ECDH_AES_KEY_WRAP path.
Restricts local users and processes to the minimum privileges needed to invoke C_WrapKey on the openCryptoki library, reducing the attack surface for supplying malicious EC keys.
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.
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.