CVE-2025-23083

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.

Published: 2025-01-22 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-23083 is rated Moderate Risk (40.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.10%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-23083

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-01 0.01% 0.10% +0.09%
2 2025-11-21 0.07% 0.01% -0.06%
3 2025-11-18 — 0.07% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-23083

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.7 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.5 5.2 [email protected]

Weakness enumeration for CVE-2025-23083

OS Trackers for CVE-2025-23083

vendor priority summary link
alpine — CVE-2025-23083: 3 source package rows (nodejs, openjdk17, openjdk21); 9 state rows across 6 repos (3.21-community, 3.21-main, 3.22-community, 3.22-main, edge-community, edge-main); fixed 9, open 0. https://security.alpinelinux.org/vuln/CVE-2025-23083
debian unimportant CVE-2025-23083 unimportant priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-23083
gentoo high CVE-2025-23083: 1 GLSA(s) (202506-08), 1 atom(s) (net-libs/nodejs); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-23083
redhat high — https://access.redhat.com/security/cve/CVE-2025-23083
suse high CVE-2025-23083 severity important: SUSE including 78 source package names (0.0.17-1.1:nodejs22-22.13.1-150600.13.6.1, 0.0.17-1.1:npm22-22.13.1-150600.13.6.1, …), 206 product×package rows across 28 product lines (Container bci/nodejs, Container containers/open-webui, … (28 product lines)): Known Not Affected 127, Fixed 79. https://www.suse.com/security/cve/CVE-2025-23083/
ubuntu medium CVE-2025-23083 medium priority: Ubuntu including 1 source packages (nodejs), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 7, ignored 2, released 1. https://ubuntu.com/security/CVE-2025-23083

Affected software / configurations for CVE-2025-23083

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-23083

cvelogic Threat Intelligence