CVE-2026-44519
MEDIUMDescription
liboqs is a C-language cryptographic library that provides implementations of post-quantum cryptography algorithms. Prior to 0.16.0, the ct_select function in src/kem/frodokem/external/util.c for the FrodoKEM-640, FrodoKEM-976, and FrodoKEM-1344 AES and SHAKE reference variants lacks a value barrier in the Fujisaki-Okamoto implicit-rejection path. When compiled with Clang 17 or later at an affected optimization level such as -Os, the compiler can emit a secret-dependent conditional load, causing the real and rejection secret paths to leave distinguishable cache residency after successful and failed decapsulation. A local attacker able to perform repeated cache-timing measurements may use this oracle as part of a private-key recovery attack. Default -O3 builds vectorize both source loads and do not exhibit the reported behavior, and the advisory does not report the same generated memory-access pattern in NTRU, NTRU-Prime, BIKE, HQC, Classic McEliece, Kyber, or the already-barriered ML-KEM implementation. This issue is fixed in version 0.16.0.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 2% of all known CVEs.
References
Related Vulnerabilities
Other CWE-385 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2018-10845 | Medium | 5.9 | 3.6% | - | Fix |
| CVE-2018-10844 | Medium | 5.9 | 3.6% | - | Fix |
| CVE-2020-25659 | Medium | 5.9 | 2.5% | - | Fix |
| CVE-2020-25657 | Medium | 5.9 | 1.8% | - | Fix |
| CVE-2020-25658 | High | 7.5 | 1.7% | - | Fix |
| CVE-2025-9231 | Medium | 5.9 | 1.6% | - | Fix |
Common questions
How do I fix CVE-2026-44519?
No published fix for CVE-2026-44519 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-44519 being actively exploited?
Not that we know of. CVE-2026-44519 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.12% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.
How severe is CVE-2026-44519?
CVE-2026-44519 has a CVSS v3 base score of 5.1, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-44519
Markdown
[](https://tridentstack.com/cve/CVE-2026-44519)HTML
<a href="https://tridentstack.com/cve/CVE-2026-44519"><img src="https://tridentstack.com/cve/badge/CVE-2026-44519.svg" alt="CVE-2026-44519"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-12.