Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.42% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2025
CVE-2025-23083High confidence
This vulnerability affects Permission Model users (--permission) on Node.js v20, v22, and v23
NodeJS · Node
7.7HighCVSS 3.0
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs NodeJS Node and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
13 package statesRelease-specific package status
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | openjdk17 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 17.0.15_p6-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | openjdk21 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 21.0.7_p6-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · main | nodejs | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 22.13.1-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · community | openjdk17 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 17.0.15_p6-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | openjdk21 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 21.0.7_p6-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · main | nodejs | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 22.13.1-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · community | openjdk17 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 17.0.15_p6-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Alpine v3.21v3.21 · community | openjdk21 | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 21.0.7_p6-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Alpine v3.21v3.21 · main | nodejs | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 22.13.1-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | nodejs | Vendor fix publishedDebian records a fixed source-package version for this release. | 20.18.2+dfsg-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | nodejs | Not affectedDebian marks this release not affected (fixed-version marker 0). | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | nodejs | Vendor fix publishedDebian records a fixed source-package version for this release. | 20.18.2+dfsg-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | nodejs | Vendor fix publishedDebian records a fixed source-package version for this release. | 20.18.2+dfsg-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2025-23083 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynodejs: Node.js Worker Thread Exposure via Diagnostics Channel
The vendor explicitly identifies these products as affected by this CVE.
- nodejs as a component of Red Hat Enterprise Linux 10
- nodejs-devel as a component of Red Hat Enterprise Linux 10
- nodejs-docs as a component of Red Hat Enterprise Linux 10
- nodejs-full-i18n as a component of Red Hat Enterprise Linux 10
- nodejs-libs as a component of Red Hat Enterprise Linux 10
- nodejs-npm as a component of Red Hat Enterprise Linux 10
- nodejs22.src as a component of Red Hat Enterprise Linux 10
- Summary
- A flaw was found in the Node.js diagnostics_channel. This vulnerability allows an attacker to reinstate and misuse worker constructors, potentially bypassing the Permission Model via hooking into events when a worker thread is created.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
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.
What
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.
Why
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How
An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How
An attacker operating through local access may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Improper Access Control → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-284 ↗
CWE-284: Improper Access Control. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NCommon Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- nodejs as a component of Red Hat Enterprise Linux 10
- nodejs-devel as a component of Red Hat Enterprise Linux 10
- nodejs-docs as a component of Red Hat Enterprise Linux 10
- nodejs-full-i18n as a component of Red Hat Enterprise Linux 10
- nodejs-libs as a component of Red Hat Enterprise Linux 10
- nodejs-npm as a component of Red Hat Enterprise Linux 10
- nodejs22.src as a component of Red Hat Enterprise Linux 10
- Fixed
- nodejs-1:20.18.2-1.module+el8.10.0+22767+a3309b10.aarch64 (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-1:20.18.2-1.module+el8.10.0+22767+a3309b10.ppc64le (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-1:20.18.2-1.module+el8.10.0+22767+a3309b10.s390x (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-1:20.18.2-1.module+el8.10.0+22767+a3309b10.src (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-1:20.18.2-1.module+el8.10.0+22767+a3309b10.x86_64 (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-1:22.13.1-1.module+el8.10.0+22759+46b58560.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-1:22.13.1-1.module+el8.10.0+22759+46b58560.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-1:22.13.1-1.module+el8.10.0+22759+46b58560.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-1:22.13.1-1.module+el8.10.0+22759+46b58560.src (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-1:22.13.1-1.module+el8.10.0+22759+46b58560.x86_64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debuginfo-1:20.18.2-1.module+el8.10.0+22767+a3309b10.aarch64 (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debuginfo-1:20.18.2-1.module+el8.10.0+22767+a3309b10.ppc64le (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debuginfo-1:20.18.2-1.module+el8.10.0+22767+a3309b10.s390x (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debuginfo-1:20.18.2-1.module+el8.10.0+22767+a3309b10.x86_64 (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debuginfo-1:22.13.1-1.module+el8.10.0+22759+46b58560.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debuginfo-1:22.13.1-1.module+el8.10.0+22759+46b58560.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debuginfo-1:22.13.1-1.module+el8.10.0+22759+46b58560.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debuginfo-1:22.13.1-1.module+el8.10.0+22759+46b58560.x86_64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debugsource-1:20.18.2-1.module+el8.10.0+22767+a3309b10.aarch64 (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debugsource-1:20.18.2-1.module+el8.10.0+22767+a3309b10.ppc64le (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debugsource-1:20.18.2-1.module+el8.10.0+22767+a3309b10.s390x (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debugsource-1:20.18.2-1.module+el8.10.0+22767+a3309b10.x86_64 (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debugsource-1:22.13.1-1.module+el8.10.0+22759+46b58560.aarch64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debugsource-1:22.13.1-1.module+el8.10.0+22759+46b58560.ppc64le (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debugsource-1:22.13.1-1.module+el8.10.0+22759+46b58560.s390x (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-debugsource-1:22.13.1-1.module+el8.10.0+22759+46b58560.x86_64 (nodejs:22) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-devel-1:20.18.2-1.module+el8.10.0+22767+a3309b10.aarch64 (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-devel-1:20.18.2-1.module+el8.10.0+22767+a3309b10.ppc64le (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-devel-1:20.18.2-1.module+el8.10.0+22767+a3309b10.s390x (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- nodejs-devel-1:20.18.2-1.module+el8.10.0+22767+a3309b10.x86_64 (nodejs:20) as a component of Red Hat Enterprise Linux AppStream (v. 8)
- and 149 more
- Action
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 22 Jan 2025 · Last source change 26 Feb 2026, 19:08 UTC · CWE-284 · Improper Access Control
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2025-3111
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCISA ADP
NVD statusNVD not scheduled
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- 4.0 < 4.*; 5.0 < 5.*; 6.0 < 6.*; 7.0 < 7.*; 8.0 < 8.*; 9.0 < 9.*; 10.0 < 10.*; 11.0 < 11.* · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 4.0 < 4.*; 5.0 < 5.*; 6.0 < 6.*; 7.0 < 7.*; 8.0 < 8.*; 9.0 < 9.*; 10.0 < 10.*; 11.0 < 11.* · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.