CVE-2026-47738 · Package
NO FIX YET · SEE WHAT TO DO
liboqs is a C post-quantum cryptography library. Before 0.16.0, calling OQS_KEM_encaps_derand on six NTRU KEMs dereferences an uninitialized function pointer, which an attacker can use to crash the calling process.
first public Nov 2, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Only applications that create one of the six NTRU KEM objects and call OQS_KEM_encaps_derand on it are exposed. The supported impact is a crash of the calling process, so services that never use derandomized encapsulation with these schemes can skip it.
Not affected if no-derandomized-encapsulation, no-ntru-kem
Who cares c, liboqs, post-quantum
liboqs in your package manager or OQS_VERSION_TEXT in oqs/oqs.h.OQS_KEM_encaps_derand and for instantiation of OQS_KEM_ntru_hps2048509, OQS_KEM_ntru_hps2048677, OQS_KEM_ntru_hps4096821, OQS_KEM_ntru_hps40961229, OQS_KEM_ntru_hrss701 or OQS_KEM_ntru_hrss1373.liboqs is a C-language cryptographic library that provides implementations of post-quantum cryptography algorithms. Prior to 0.16.0, OQS_KEM_encaps_derand can dereference an uninitialized encaps_derand function pointer when called on NTRU-HPS-2048-509, NTRU-HPS-2048-677, NTRU-HPS-4096-821, NTRU-HPS-4096-1229, NTRU-HRSS-701, or NTRU-HRSS-1373. The affected NTRU constructors omit the OQS_KEM.encaps_derand member because those schemes do not support derandomized encapsulation, OQS_KEM objects are allocated without zero initialization, and the wrapper in src/kem/kem.c checks only that the OQS_KEM pointer is non-null before calling through the residual heap value. An application is affected only if it instantiates one of those six NTRU KEMs and invokes OQS_KEM_encaps_derand on it. The supported impact is a calling-process crash and denial of service. This issue is fixed in version 0.16.0.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
0.16.0NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.