# CVE-2025-23166: Denial of service in node > An attacker can remotely crash the Node.js runtime by supplying crafted inputs to cryptographic operations, causing a denial of service. - **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 May 2025 - **Updated:** 28 May 2025 - **Also known as:** ALPINE-CVE-2025-23166, ALSA-2025:8467, ALSA-2025:8468, ALSA-2025:8493, ALSA-2025:8506, ALSA-2025:8514, AZL-61919, AZL-65066, BELL-CVE-2025-23166, BIT-node-2025-23166, BIT-node-min-2025-23166, CLSA-2025-1753208069, CLSA-2026-1770140451, DEBIAN-CVE-2025-23166, GHSA-rrjv-57mm-j6cm, MINI-2prp-x8rh-8mp7, MINI-3vg7-jpx8-vxc8, MINI-9mpm-m2v9-52c3, MINI-v75q-79p7-9qw6, MINI-v8rv-8mgh-626r, RHSA-2025:8902, UBUNTU-CVE-2025-23166 ## What is CVE-2025-23166? CVE-2025-23166 is a high-severity denial of service vulnerability in nodejs node, published on 19 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background thread, crashing the Node.js process. Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism potentially allows an adversary to remotely crash a Node.js runtime. Weakness: CWE-248 (Uncaught Exception) ## Which versions are affected by CVE-2025-23166? 2 open source packages ship an affected version, including node and node-min. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `node` | Bitnami | All versions | 20.19.2, 22.15.1, 24.0.2 | | `node-min` | Bitnami | All versions | 20.19.2, 22.15.1, 24.0.2 | | `nodejs-docs` | AlmaLinux:10 | All versions | 1:22.16.0-1.el10_0 | | `nodejs` | AlmaLinux:8 | All versions | 1:20.19.2-1.module_el8.10.0+4007+01f7d99b | | `nodejs` | AlmaLinux:8 | All versions | 1:22.16.0-1.module_el8.10.0+4006+3c416519 | | `nodejs-devel` | AlmaLinux:8 | All versions | 1:20.19.2-1.module_el8.10.0+4007+01f7d99b | | `nodejs-devel` | AlmaLinux:8 | All versions | 1:22.16.0-1.module_el8.10.0+4006+3c416519 | | `nodejs-docs` | AlmaLinux:8 | All versions | 1:20.19.2-1.module_el8.10.0+4007+01f7d99b | | `nodejs-docs` | AlmaLinux:8 | All versions | 1:22.16.0-1.module_el8.10.0+4006+3c416519 | | `nodejs-full-i18n` | AlmaLinux:8 | All versions | 1:20.19.2-1.module_el8.10.0+4007+01f7d99b | | `nodejs-full-i18n` | AlmaLinux:8 | All versions | 1:22.16.0-1.module_el8.10.0+4006+3c416519 | | `nodejs-libs` | AlmaLinux:8 | All versions | 1:22.16.0-1.module_el8.10.0+4006+3c416519 | | `nodejs-nodemon` | AlmaLinux:8 | All versions | 3.0.1-1.module_el8.10.0+3982+85c136aa | | `nodejs-nodemon` | AlmaLinux:8 | All versions | 3.0.1-1.module_el8.10.0+3983+391a1a04 | | `nodejs-packaging` | AlmaLinux:8 | All versions | 2021.06-4.module_el8.10.0+3987+dbda4426 | | `nodejs-packaging` | AlmaLinux:8 | All versions | 2021.06-4.module_el8.10.0+4006+3c416519 | | `nodejs-packaging-bundler` | AlmaLinux:8 | All versions | 2021.06-4.module_el8.10.0+3958+472a6467 | | `nodejs-packaging-bundler` | AlmaLinux:8 | All versions | 2021.06-4.module_el8.10.0+3961+6a788e57 | | `npm` | AlmaLinux:8 | All versions | 1:10.8.2-1.20.19.2.1.module_el8.10.0+4007+01f7d99b | | `npm` | AlmaLinux:8 | All versions | 1:10.9.2-1.22.16.0.1.module_el8.10.0+4006+3c416519 | | `v8-12.4-devel` | AlmaLinux:8 | All versions | 3:12.4.254.21-1.22.16.0.1.module_el8.10.0+4006+3c416519 | | `nodejs` | AlmaLinux:9 | All versions | 1:20.19.2-1.module_el9.6.0+169+c9cb05c2 | | `nodejs` | AlmaLinux:9 | All versions | 1:22.16.0-1.module_el9.6.0+170+f035de78 | | `nodejs-devel` | AlmaLinux:9 | All versions | 1:20.19.2-1.module_el9.6.0+169+c9cb05c2 | | `nodejs-devel` | AlmaLinux:9 | All versions | 1:22.16.0-1.module_el9.6.0+170+f035de78 | | `nodejs-docs` | AlmaLinux:9 | All versions | 1:20.19.2-1.module_el9.6.0+169+c9cb05c2 | | `nodejs-docs` | AlmaLinux:9 | All versions | 1:22.16.0-1.module_el9.6.0+170+f035de78 | | `nodejs-full-i18n` | AlmaLinux:9 | All versions | 1:20.19.2-1.module_el9.6.0+169+c9cb05c2 | | `nodejs-full-i18n` | AlmaLinux:9 | All versions | 1:22.16.0-1.module_el9.6.0+170+f035de78 | | `nodejs-libs` | AlmaLinux:9 | All versions | 1:22.16.0-1.module_el9.6.0+170+f035de78 | | `nodejs-nodemon` | AlmaLinux:9 | All versions | 3.0.1-1.module_el9.5.0+125+8dc38870 | | `nodejs-nodemon` | AlmaLinux:9 | All versions | 3.0.1-1.module_el9.5.0+139+09296491 | | `nodejs-packaging` | AlmaLinux:9 | All versions | 2021.06-4.module_el9.5.0+139+09296491 | | `nodejs-packaging` | AlmaLinux:9 | All versions | 2021.06-4.module_el9.6.0+162+8dc602e5 | | `nodejs-packaging-bundler` | AlmaLinux:9 | All versions | 2021.06-4.module_el9.5.0+139+09296491 | | `nodejs-packaging-bundler` | AlmaLinux:9 | All versions | 2021.06-4.module_el9.6.0+162+8dc602e5 | | `npm` | AlmaLinux:9 | All versions | 1:10.8.2-1.20.19.2.1.module_el9.6.0+169+c9cb05c2 | | `npm` | AlmaLinux:9 | All versions | 1:10.9.2-1.22.16.0.1.module_el9.6.0+170+f035de78 | | `v8-12.4-devel` | AlmaLinux:9 | All versions | 3:12.4.254.21-1.22.16.0.1.module_el9.6.0+170+f035de78 | | `nodejs` | Red Hat:rhel_eus:9.4::appstream | All versions | 1:20.19.2-2.module+el9.4.0+23180+d266bac7 | ## How do I fix CVE-2025-23166? Upgrade node to a fixed version for your release line: 20.19.2, 22.15.1 or 24.0.2. ## Is CVE-2025-23166 being exploited? There is no known exploitation of CVE-2025-23166 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-23166 and fix it if it is affected. What it is: CVE-2025-23166 is a high-severity denial of service vulnerability in nodejs node, published on 19 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-23166 in the wild and no public exploit code. Affected packages and fixed versions: - node (Bitnami): affected all versions; fixed in 20.19.2, 22.15.1, 24.0.2 - node-min (Bitnami): affected all versions; fixed in 20.19.2, 22.15.1, 24.0.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-23166/ (Markdown: https://insights.sbomify.com/CVE-2025-23166/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23166 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23166 - OSV: https://osv.dev/vulnerability/CVE-2025-23166 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-23166/ Summaries are generated and may contain mistakes; the official description above is the record.