Skip to content
Noroxi
NVD / CVE Program· CNA hackerone

CVE-2023-32559: A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x.

Noroxi assessment

Priority: Monitor (action score 31/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: 1.8% (FIRST EPSS); higher than 78.6% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: NodeJS Node 10.*, 11.*, 12.*.

Low priority for now. Upgrade to NodeJS Node 10.*, 11.*, 12.* 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

A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API `process.binding()` can bypass the policy mechanism by requiring internal modules and eventually take advantage of `process.binding('spawn_sync')` run arbitrary code, outside of the limits defined in a `policy.json` file. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Aug 23, 2023
Updated
Jun 17, 2026
EPSS
1.8% · 78th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

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-2023-32559

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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.

Running WordPress? Scan your site free with WP Lens

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.

VendorProduct
nodejsnode.js

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

Watch new CVEs for node.js

When you'll hear from us

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

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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.

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs node.js16.0.0 and later · up to 16.20.1 inclusive
  • nodejs node.js18.0.0 and later · up to 18.17.0 inclusive
  • nodejs node.js20.0.0 and later · up to 20.5.0 inclusive

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:18.17.1-1.module_el8.8.0+3613+1ed8c91d1:18.17.1-1.module_el8.8.0+3613+1ed8c91d
AlmaLinux:8nodejsbefore 1:16.20.2-2.module_el8.8.0+3614+204d6f431:16.20.2-2.module_el8.8.0+3614+204d6f43
AlmaLinux:8nodejs-develbefore 1:18.17.1-1.module_el8.8.0+3613+1ed8c91d1:18.17.1-1.module_el8.8.0+3613+1ed8c91d
AlmaLinux:8nodejs-develbefore 1:16.20.2-2.module_el8.8.0+3614+204d6f431:16.20.2-2.module_el8.8.0+3614+204d6f43
AlmaLinux:8nodejs-docsbefore 1:16.20.2-2.module_el8.8.0+3614+204d6f431:16.20.2-2.module_el8.8.0+3614+204d6f43
AlmaLinux:8nodejs-docsbefore 1:18.17.1-1.module_el8.8.0+3613+1ed8c91d1:18.17.1-1.module_el8.8.0+3613+1ed8c91d
AlmaLinux:8nodejs-full-i18nbefore 1:18.17.1-1.module_el8.8.0+3613+1ed8c91d1:18.17.1-1.module_el8.8.0+3613+1ed8c91d
AlmaLinux:8nodejs-full-i18nbefore 1:16.20.2-2.module_el8.8.0+3614+204d6f431:16.20.2-2.module_el8.8.0+3614+204d6f43
AlmaLinux:8nodejs-nodemonbefore 3.0.1-1.module_el8.8.0+3614+204d6f433.0.1-1.module_el8.8.0+3614+204d6f43
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 26-1.module_el8.8.0+3614+204d6f4326-1.module_el8.8.0+3614+204d6f43
AlmaLinux:8nodejs-packagingbefore 2021.06-4.module_el8.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-4.module_el8.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8npmbefore 1:8.19.4-1.16.20.2.2.module_el8.8.0+3614+204d6f431:8.19.4-1.16.20.2.2.module_el8.8.0+3614+204d6f43
AlmaLinux:8npmbefore 1:9.6.7-1.18.17.1.1.module_el8.8.0+3613+1ed8c91d1:9.6.7-1.18.17.1.1.module_el8.8.0+3613+1ed8c91d
AlmaLinux:9nodejsbefore 1:18.17.1-1.module_el9.2.0+36+853e48f51:18.17.1-1.module_el9.2.0+36+853e48f5
AlmaLinux:9nodejsbefore 1:16.20.2-1.el9_21:16.20.2-1.el9_2
AlmaLinux:9nodejs-develbefore 1:18.17.1-1.module_el9.2.0+36+853e48f51:18.17.1-1.module_el9.2.0+36+853e48f5
AlmaLinux:9nodejs-docsbefore 1:18.17.1-1.module_el9.2.0+36+853e48f51:18.17.1-1.module_el9.2.0+36+853e48f5
AlmaLinux:9nodejs-docsbefore 1:16.20.2-1.el9_21:16.20.2-1.el9_2
AlmaLinux:9nodejs-full-i18nbefore 1:16.20.2-1.el9_21:16.20.2-1.el9_2
AlmaLinux:9nodejs-full-i18nbefore 1:18.17.1-1.module_el9.2.0+36+853e48f51:18.17.1-1.module_el9.2.0+36+853e48f5
AlmaLinux:9nodejs-libsbefore 1:16.20.2-1.el9_21:16.20.2-1.el9_2
AlmaLinux:9nodejs-nodemonbefore 3.0.1-1.module_el9.2.0+36+853e48f53.0.1-1.module_el9.2.0+36+853e48f5

+96

Other highest-scoring records for the same primary product.

  • CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed
    56Plan
  • CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an
    53Plan
  • CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c
    50Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-32006Aug 15, 2023 · The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition fo
    35Monitor
  • ← EarlierCVE-2023-32002Aug 21, 2023 · The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module.
    39Monitor
  • Later →CVE-2023-32005Sep 11, 2023 · A vulnerability has been identified in Node.js version 20, affecting users of the experimental permission model when the --allow-fs-read fla
    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.20.2Vendor (CNA)
NodeJS Node17.*Vendor (CNA)
NodeJS Node18.17.1Vendor (CNA)
NodeJS Node19.*Vendor (CNA)
NodeJS Node20.5.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)
almalinux:nodejs1:16.20.2-2.module_el8.8.0+3614+204d6f43 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-devel1:16.20.2-2.module_el8.8.0+3614+204d6f43 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-docs1:16.20.2-2.module_el8.8.0+3614+204d6f43 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-full-i18n1:16.20.2-2.module_el8.8.0+3614+204d6f43 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-libs1:16.20.2-1.el9_2 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-nodemon3.0.1-1.module_el8.8.0+3614+204d6f43 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging26-1.module_el8.8.0+3614+204d6f43 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging-bundler2021.06-4.module_el8.7.0+3343+ea2b7901 · AlmaLinux:8Package registry (OSV)
almalinux:npm1:8.19.4-1.16.20.2.2.module_el8.8.0+3614+204d6f43 · AlmaLinux:8Package registry (OSV)
alpine:nodejs16.20.2-r0 · Alpine:v3.15Package registry (OSV)
debian:nodejs18.19.0+dfsg-6~deb12u1 · Debian:12Package registry (OSV)
opensuse:nodejs1212.22.12-150200.4.50.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:nodejs1414.21.3-150200.15.49.1 · openSUSE:Leap 15.4Package registry (OSV)

+25

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

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

—

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • CVE-2023-320022 days apartThe use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module.
    39Monitor

Bug bounty scope

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

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

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

CVSS vector

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

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml
kind: ClusterRolerules:  - apiGroups: ["*"]    resources: ["*"]    verbs: ["*"]

Fixed

yaml
kind: Rolemetadata:  namespace: lodos-systemrules:  - apiGroups: ["apps"]    resources: ["deployments"]    verbs: ["get", "list", "update"]

Attack context

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

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

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

All records