Skip to main content
CVE-2026-44519VulnerabilityPublished

FO implicit rejection path (FrodoKEM, NTRU · liboqs: Missing value barrier

Affects MicrosoftSource GCVE Database

0
Compare
Authoritative record:CVE-2026-44519· Medium 5.1

Not known to be exploited · CVSS 5.1 Medium : upgrade to 0.16.0 when convenient.

Data as of 17 Nov 2026, 10:20 UTC

CVSS 3.1 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.1
Patch
Available – fixed in 0.16.0
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade liboqs and open-quantum-safe/liboqs to 0.16.0.

Affected software

ProductAffectedFixed in
open-quantum-safeliboqsAffected
  • <0.16.0
Fixed in
  • 0.16.0
GitHubopen-quantum-safe/liboqspkg:github/open-quantum-safe/liboqsOther threatsAffected
  • <0.16.0
Fixed in
  • 0.16.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle: https://support.microsoft.com/lifecycle

References

Community reviews

Loading reviews…