# CVE-2025-23083: Security feature bypass in Node > Attackers can bypass Node.js permission model restrictions by hooking into worker thread creation via diagnostics_channel to access internal workers. - **Severity:** High 7.7 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jan 2025 - **Updated:** 26 Feb 2026 - **Also known as:** ALPINE-CVE-2025-23083, AZL-55922, BELL-CVE-2025-23083, BIT-node-2025-23083, BIT-node-min-2025-23083, DEBIAN-CVE-2025-23083, GHSA-wv7p-rjf3-9fr5, MINI-6xr9-f47m-wx3f, MINI-f9p3-f44v-h6ww, MINI-mr58-gm9g-cvjv, MINI-p296-v55m-rjg4, OESA-2025-1234, OESA-2025-1235, RHSA-2025:1522 ## What is CVE-2025-23083? CVE-2025-23083 is a high-severity vulnerability in NodeJS Node, published on 22 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description With the aid of the diagnostics_channel utility, an event can be hooked into whenever a worker thread is created. This is not limited only to workers but also exposes internal workers, where an instance of them can be fetched, and its constructor can be grabbed and reinstated for malicious usage. This vulnerability affects Permission Model users (--permission) on Node.js v20, v22, and v23. Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2025-23083? 2 open source packages ship an affected version, including node and node-min. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `node` | Bitnami | From 19.0.0 | 20.18.2, 22.13.1, 23.8.0 | | `node-min` | Bitnami | From 19.0.0 | 20.18.2, 22.13.1, 23.8.0 | | `nodejs` | Red Hat:rhel_eus:9.4::appstream | All versions | 1:20.18.2-1.module+el9.4.0+22789+7c201776 | | `nodejs-debuginfo` | Red Hat:rhel_eus:9.4::appstream | All versions | 1:20.18.2-1.module+el9.4.0+22789+7c201776 | | `nodejs-debugsource` | Red Hat:rhel_eus:9.4::appstream | All versions | 1:20.18.2-1.module+el9.4.0+22789+7c201776 | | `nodejs-devel` | Red Hat:rhel_eus:9.4::appstream | All versions | 1:20.18.2-1.module+el9.4.0+22789+7c201776 | | `nodejs-docs` | Red Hat:rhel_eus:9.4::appstream | All versions | 1:20.18.2-1.module+el9.4.0+22789+7c201776 | | `nodejs-full-i18n` | Red Hat:rhel_eus:9.4::appstream | All versions | 1:20.18.2-1.module+el9.4.0+22789+7c201776 | | `nodejs-nodemon` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:3.0.1-1.module+el9.3.0.z+20478+84a9f781 | | `nodejs-packaging` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:2021.06-4.module+el9.3.0+19518+63aad52d | | `nodejs-packaging-bundler` | Red Hat:rhel_eus:9.4::appstream | All versions | 0:2021.06-4.module+el9.3.0+19518+63aad52d | | `npm` | Red Hat:rhel_eus:9.4::appstream | All versions | 1:10.8.2-1.20.18.2.1.module+el9.4.0+22789+7c201776 | ## How do I fix CVE-2025-23083? Upgrade node to a fixed version for your release line: 20.18.2, 22.13.1 or 23.8.0. ## Is CVE-2025-23083 being exploited? There is no known exploitation of CVE-2025-23083 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-23083 and fix it if it is affected. What it is: CVE-2025-23083 is a high-severity vulnerability in NodeJS Node, published on 22 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-23083 in the wild and no public exploit code. Affected packages and fixed versions: - node (Bitnami): affected from 19.0.0; fixed in 20.18.2, 22.13.1, 23.8.0 - node-min (Bitnami): affected from 19.0.0; fixed in 20.18.2, 22.13.1, 23.8.0 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-23083/ (Markdown: https://insights.sbomify.com/CVE-2025-23083/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23083 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23083 - OSV: https://osv.dev/vulnerability/CVE-2025-23083 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-23083/ Summaries are generated and may contain mistakes; the official description above is the record.