All vulnerabilities

Servers and applications

CVE-2026-49440

Miller-Rabin Primality Test Allows Zero Rounds

Severity
High 7.4
Published
27 May 2026
Last changed
25 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
2.8.1
Exploit chance
0.2% in the next 30 daysHigher than 14% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
CWE-325
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Read data · Change data
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Also known as
GHSA-9xg4-qhm4-g43w
Sources
NVD, Project advisories (GitHub)

Description

node:crypto.checkPrime(candidate[, options][, callback]) and crypto.checkPrimeSync(candidate[, options]) ran no Miller-Rabin rounds at all when the caller left options.checks at its default of 0. In that mode, the only test applied to the candidate was trial division by the primes up to 17,863. Any composite whose smallest prime factor exceeds that bound — for example the product of two primes just above it, such as 17,881 × 17,891 — was reported as true ("probably prime").

The same divergence affected the lower-level op_node_check_prime / op_node_check_prime_bytes paths that the polyfill calls into.

Node.js itself does not have this problem: it forwards checks = 0 to OpenSSL's BN_check_prime, which substitutes a sensible default number of rounds based on the candidate's bit length (per FIPS 186-4 Appendix C.3 Table C.1). Deno's Rust implementation had no equivalent fallback, so count = 0 meant "skip the loop entirely."

From denoland/deno's security advisory. Shortened; the full text is there.

Workarounds

If you cannot upgrade immediately:

  • Pass an explicit checks value when calling crypto.checkPrime or crypto.checkPrimeSync. A value of 64 is conservative for any reasonable bit length and keeps the loop running.
  • Do not rely on crypto.checkPrime to validate attacker-influenced bignums in security-critical paths until you are on the patched release.
Workarounds as given by denoland/deno's security advisory.

Affected software

SoftwareAffected versions
DenoServers and applications · cpe:a:deno:deno
  • Every version before 2.8.1
DenoServers and applications · github:denoland/deno
  • Every version before 2.8.1

About Deno

secure runtime for JavaScript and TypeScript based on the V8 JavaScript engine and the Rust programming language

From Wikidata, CC0 1.0.
Monthly active users
400k+Deno
Developers who used it in the past year
4%Stack Overflow Developer Survey 2025, 2025
Weekly downloads (npm)
530,707npm, 15 Nov 2026
Downloads in the last 90 days (crates.io)
2,447crates.io, 15 Nov 2026
Total downloads (crates.io)
634,116crates.io, 15 Nov 2026
Docker Hub pulls
9,367,609Docker Hub, 15 Nov 2026
GitHub stars
108,888GitHub, 15 Nov 2026
Forks
7,444GitHub, 15 Nov 2026
Latest release
v2.9.8GitHub, 15 Nov 2026
Released
21 Oct 2026GitHub
Developer
Ryan DahlWikidata
License
MIT LicenseWikidata
Written in
Rust, TypeScript, JavaScriptWikidata
First released
13 May 2018Wikidata
First published on GitHub
15 May 2018GitHub

Release lines

ReleaseLatestSecurity fixes
2.92.9.8Yes
2.82.8.3Ended 25 Jun 2026
2.72.7.14Ended 22 May 2026
2.62.6.10Ended 25 Feb 2026
2.5 (LTS)LTS2.5.7Ended 30 Apr 2026
2.42.4.5Ended 10 Sept 2025

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-49440
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-49440
  • GitHub Advisory Database https://github.com/advisories/GHSA-9xg4-qhm4-g43w
  • github.com https://github.com/denoland/deno/security/advisories/GHSA-9xg4-qhm4-g43w