Skip to content
Noroxi
NVD / CVE Program· CNA hackerone

CVE-2025-23083: With the aid of the diagnostics_channel utility, an event can be hooked into whenever a worker thread is created.

HighCVSS 7.7 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: NodeJS Node 10.*, 11.*, 12.*; azl3 nodejs 20.14.0-4 on Azure Linux 3.0 20.14.0-4; azl3 nodejs 20.14.0-8 on Azure Linux 3.0 20.14.0-4.

Low priority for now. Upgrade to NodeJS Node 10.*, 11.*, 12.*; azl3 nodejs 20.14.0-4 on Azure Linux 3.0 20.14.0-4; azl3 nodejs 20.14.0-8 on Azure Linux 3.0 20.14.0-4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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
Jan 21, 2025
Updated
Jun 17, 2026
EPSS
0.4% · 37th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · hackerone
7.7
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-23083

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for nodejs records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Using node? Add it to your stack and be the first to know about CVEs like this one. (Node.js)

Watch new CVEs for node

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or is weaponized

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every Monday

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • NodeJS Node

    • 4.0 and later · before 4.*affected · semver
    • 5.0 and later · before 5.*affected · semver
    • 6.0 and later · before 6.*affected · semver
    • 7.0 and later · before 7.*affected · semver
    • 8.0 and later · before 8.*affected · semver
    • 9.0 and later · before 9.*affected · semver
    • 10.0 and later · before 10.*affected · semver
    • 11.0 and later · before 11.*affected · semver
    • 12.0 and later · before 12.*affected · semver
    • 13.0 and later · before 13.*affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8nodejsbefore 1:22.13.1-1.module_el8.10.0+3961+6a788e571:22.13.1-1.module_el8.10.0+3961+6a788e57
AlmaLinux:8nodejsbefore 1:20.18.2-1.module_el8.10.0+3958+472a64671:20.18.2-1.module_el8.10.0+3958+472a6467
AlmaLinux:8nodejs-develbefore 1:22.13.1-1.module_el8.10.0+3961+6a788e571:22.13.1-1.module_el8.10.0+3961+6a788e57
AlmaLinux:8nodejs-develbefore 1:20.18.2-1.module_el8.10.0+3958+472a64671:20.18.2-1.module_el8.10.0+3958+472a6467
AlmaLinux:8nodejs-docsbefore 1:20.18.2-1.module_el8.10.0+3958+472a64671:20.18.2-1.module_el8.10.0+3958+472a6467
AlmaLinux:8nodejs-docsbefore 1:22.13.1-1.module_el8.10.0+3961+6a788e571:22.13.1-1.module_el8.10.0+3961+6a788e57
AlmaLinux:8nodejs-full-i18nbefore 1:20.18.2-1.module_el8.10.0+3958+472a64671:20.18.2-1.module_el8.10.0+3958+472a6467
AlmaLinux:8nodejs-full-i18nbefore 1:22.13.1-1.module_el8.10.0+3961+6a788e571:22.13.1-1.module_el8.10.0+3961+6a788e57
AlmaLinux:8nodejs-libsbefore 1:22.13.1-1.module_el8.10.0+3961+6a788e571:22.13.1-1.module_el8.10.0+3961+6a788e57
AlmaLinux:8nodejs-nodemonbefore 3.0.1-1.module_el8.8.0+3613+1ed8c91d3.0.1-1.module_el8.8.0+3613+1ed8c91d
AlmaLinux:8nodejs-packagingbefore 2021.06-4.module_el8.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8nodejs-packagingbefore 2021.06-4.module_el8.10.0+3961+6a788e572021.06-4.module_el8.10.0+3961+6a788e57
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-4.module_el8.10.0+3958+472a64672021.06-4.module_el8.10.0+3958+472a6467
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-4.module_el8.10.0+3961+6a788e572021.06-4.module_el8.10.0+3961+6a788e57
AlmaLinux:8npmbefore 1:10.8.2-1.20.18.2.1.module_el8.10.0+3958+472a64671:10.8.2-1.20.18.2.1.module_el8.10.0+3958+472a6467
AlmaLinux:8npmbefore 1:10.9.2-1.22.13.1.1.module_el8.10.0+3961+6a788e571:10.9.2-1.22.13.1.1.module_el8.10.0+3961+6a788e57
AlmaLinux:8v8-12.4-develbefore 3:12.4.254.21-1.22.13.1.1.module_el8.10.0+3961+6a788e573:12.4.254.21-1.22.13.1.1.module_el8.10.0+3961+6a788e57
AlmaLinux:9nodejsbefore 1:20.18.2-1.module_el9.5.0+137+381f3eaf1:20.18.2-1.module_el9.5.0+137+381f3eaf
AlmaLinux:9nodejsbefore 1:22.13.1-1.module_el9.5.0+139+092964911:22.13.1-1.module_el9.5.0+139+09296491
AlmaLinux:9nodejs-develbefore 1:22.13.1-1.module_el9.5.0+139+092964911:22.13.1-1.module_el9.5.0+139+09296491
AlmaLinux:9nodejs-develbefore 1:20.18.2-1.module_el9.5.0+137+381f3eaf1:20.18.2-1.module_el9.5.0+137+381f3eaf
AlmaLinux:9nodejs-docsbefore 1:20.18.2-1.module_el9.5.0+137+381f3eaf1:20.18.2-1.module_el9.5.0+137+381f3eaf
AlmaLinux:9nodejs-docsbefore 1:22.13.1-1.module_el9.5.0+139+092964911:22.13.1-1.module_el9.5.0+139+09296491
AlmaLinux:9nodejs-full-i18nbefore 1:22.13.1-1.module_el9.5.0+139+092964911:22.13.1-1.module_el9.5.0+139+09296491

+95

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2…
    57Plan
  • CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.
    34Monitor
  • CVE-2026-123872Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change
    32Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-27980Jan 8, 2025 · Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject…
    32Monitor
  • ← EarlierCVE-2024-37372Jan 8, 2025 · The Permission Model assumes that any path starting with two backslashes \ has a four-character prefix that can be ignored, which is not…
    14Monitor
  • Later →CVE-2025-23085Feb 7, 2025 · A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification.
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
NodeJS Node10.*Vendor (CNA)
NodeJS Node11.*Vendor (CNA)
NodeJS Node12.*Vendor (CNA)
NodeJS Node13.*Vendor (CNA)
NodeJS Node14.*Vendor (CNA)
NodeJS Node15.*Vendor (CNA)
NodeJS Node16.*Vendor (CNA)
NodeJS Node17.*Vendor (CNA)
NodeJS Node19.*Vendor (CNA)
NodeJS Node20.18.2Vendor (CNA)
NodeJS Node21.*Vendor (CNA)
NodeJS Node22.13.1Vendor (CNA)
NodeJS Node23.6.1Vendor (CNA)
NodeJS Node4.*Vendor (CNA)
NodeJS Node5.*Vendor (CNA)
NodeJS Node6.*Vendor (CNA)
NodeJS Node7.*Vendor (CNA)
NodeJS Node8.*Vendor (CNA)
NodeJS Node9.*Vendor (CNA)
azl3 nodejs 20.14.0-4 on Azure Linux 3.020.14.0-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 nodejs 20.14.0-8 on Azure Linux 3.020.14.0-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:nodejs1:20.18.2-1.module_el8.10.0+3958+472a6467 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-devel1:20.18.2-1.module_el8.10.0+3958+472a6467 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-docs1:20.18.2-1.module_el8.10.0+3958+472a6467 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-full-i18n1:20.18.2-1.module_el8.10.0+3958+472a6467 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-libs1:22.13.1-1.module_el8.10.0+3961+6a788e57 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-nodemon3.0.1-1.module_el8.8.0+3613+1ed8c91d · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging2021.06-4.module_el8.7.0+3343+ea2b7901 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging-bundler2021.06-4.module_el8.10.0+3958+472a6467 · AlmaLinux:8Package registry (OSV)
almalinux:npm1:10.8.2-1.20.18.2.1.module_el8.10.0+3958+472a6467 · AlmaLinux:8Package registry (OSV)

+27

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-30583136 days apartfs.openAsBlob() can bypass the experimental permission model when using the file system read restriction with the `--allow-fs-read` flag in…
    30Monitor
  • CVE-2023-30587136 days apartA vulnerability in Node.js version 20 allows for bypassing restrictions set by the --experimental-permission flag using the built-in…
    30Monitor
  • CVE-2023-30582136 days apartA vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read…
    21Monitor

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-284 · Improper Access Control

CVSS vector

CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records