Cyber Resilience

CVE-2026-49440

Deno ≤ 2.8.1

Published
23 June 2026
Modified
26 June 2026
CVSS Score v3.1 7.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0015 5th percentile
Risk Priority 53 floored blend · peak EPSS

Summary

CVE-2026-49440 is a high-severity Missing Cryptographic Step (CWE-325) vulnerability in Deno Deno. Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Weaken Encryption (T1600); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8.1, 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…

more

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. This vulnerability is fixed in 2.8.1.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1600 Weaken Encryption Defense Impairment
Adversaries may compromise a network device’s encryption capability in order to bypass encryption that would otherwise protect data communications.
T1600.001 Reduce Key Space Defense Impairment
Adversaries may reduce the level of effort required to decrypt data transmitted over the network by reducing the cipher strength of encrypted communications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-22863Same product: Deno Deno
CVE-2026-49859Same product: Deno Deno
CVE-2025-61786Same product: Deno Deno
CVE-2026-27190Same product: Deno Deno
CVE-2026-44726Same product: Deno Deno
CVE-2024-27933Same product: Deno Deno
CVE-2024-37150Same product: Deno Deno
CVE-2026-32260Same product: Deno Deno
CVE-2023-28446Same product: Deno Deno
CVE-2023-26103Same product: Deno Deno

Affected Assets

deno
deno
≤ 2.8.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 14 hardening rules · 6 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

Requires selection and implementation of specific approved cryptographic algorithms and methods, reducing the chance that an incomplete algorithm is used.

Mandates developer testing and evaluation that can uncover missing cryptographic steps through functional and penetration testing.

Requires documented development standards and processes that include correct cryptographic algorithm implementation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly include correct cryptographic algorithm implementation and testing.

PR.DS-01 partial match
prevents

Proper encryption of data-at-rest requires all algorithm steps; omitting one directly weakens the control.

PR.DS-02 partial match
prevents

Proper encryption of data-in-transit requires all algorithm steps; omitting one directly weakens the control.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect incomplete crypto implementations but does not itself enforce correct algorithm steps.

degrades

Mandates correct use of cryptographic controls, directly preventing omission of required algorithm steps.

prevents

Secure SDLC processes reduce the likelihood of missing crypto steps but do not guarantee algorithm completeness.

prevents

Requires secure coding practices that would catch missing cryptographic steps during development.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-325
  • V-248535 The OL 8 shadow password suite must be configured to use a sufficient number of hashing rounds. prevents CWE-325
Oracle Linux 9 (1 rule)
  • V-271454 OL 9 must enable FIPS mode. prevents CWE-325
RHEL 7 (1 rule)
  • V-204497 The Red Hat Enterprise Linux operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-325
RHEL 8 (1 rule)
  • V-230223 RHEL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-325
Ubuntu 22.04 (1 rule)
  • V-260650 Ubuntu 22.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-325
Ubuntu 24.04 (1 rule)
  • V-270744 Ubuntu 24.04 LTS must implement NIST FIPS-validated cryptography to protect classified information and for the following: To provision digital signatures, to generate cryptographic hashes, and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-325

References