CVE-2026-46344: liboqs: Heap-buffer-overflow in XMSS verification path via OID-controlled parameter mismatch (xmss_commons.c:194)
liboqs is a C-language cryptographic library that provides implementations of post-quantum cryptography algorithms. Prior to 0.16.0, an out-of-bounds read has been identified in the XMSS and XMSS^MT stateful signature verification code. When the verification function is called with a correctly-sized signature buffer for the declared algorithm but a public key whose OID bytes (pk[0..3]) reference a different XMSS parameter set with a larger sigbytes, the implementation re-parses the OID from the public key inside xmsssignopen / xmssmtsignopen and uses the resulting (larger) sigbytes to index the caller-supplied signature buffer. As with CVE-2026-44518, the out-of-bounds bytes are consumed only as input to an internal hash computation and are not returned to the caller, so no oracle exists to leak their contents to an attacker. The primary observable effect is a possible crash (denial of service) of the verifying process if the read crosses into an unmapped memory page. This vulnerability is fixed in 0.16.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
liboqsto a version that resolves this vulnerability.Fixed in 0.16.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-46344?
CVE-2026-46344 has a medium severity rating of 5.3.
How do I fix CVE-2026-46344?
To fix CVE-2026-46344, upgrade to liboqs version 0.16.0 or later.
What type of vulnerability is CVE-2026-46344?
CVE-2026-46344 is a heap-buffer-overflow vulnerability in the XMSS verification path.
What effects can CVE-2026-46344 have on my system?
CVE-2026-46344 can lead to an out-of-bounds read, potentially causing application instability.
Is CVE-2026-46344 present in all versions of liboqs?
Yes, CVE-2026-46344 affects all liboqs versions prior to 0.16.0.