Skip to content
Noroxi
NVD / CVE Program· CNA hackerone

CVE-2026-21716: An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and `FileHandle.chown()` in the promises API without the required permissio

Noroxi assessment

Priority: Monitor (action score 13/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.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: azl3 nodejs 20.14.0-14 on Azure Linux 3.0 20.14.0-15; azl3 nodejs24 24.13.0-3 on Azure Linux 3.0 24.14.1-1.

Low priority for now. Upgrade to azl3 nodejs 20.14.0-14 on Azure Linux 3.0 20.14.0-15; azl3 nodejs24 24.13.0-3 on Azure Linux 3.0 24.14.1-1 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

An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and `FileHandle.chown()` in the promises API without the required permission checks, while their callback-based equivalents (`fs.fchmod()`, `fs.fchown()`) were correctly patched. As a result, code running under `--permission` with restricted `--allow-fs-write` can still use promise-based `FileHandle` methods to modify file permissions and ownership on already-open file descriptors, bypassing the intended write restrictions. This vulnerability affects **20.x, 22.x, 24.x, and 25.x** processes using the Permission Model where `--allow-fs-write` is intentionally restricted.

LowCVSS 3.3 · v3.0—No exploit Fix available
Published
Mar 30, 2026
Updated
Aug 19, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

13

Monitor

Low priority for now.

CVSS
13 / 40 · 3.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · hackerone
3.3
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-2026-21716

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for nodejs records

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.

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

Affected versions

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

  • nodejs node.jsup to 20.20.1 inclusive
  • nodejs node.js22.0.0 and later · up to 22.22.1 inclusive
  • nodejs node.js24.0.0 and later · up to 24.14.0 inclusive
  • nodejs node.js25.0.0 and later · up to 25.8.1 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

    • 20.20.1 and later · up to and including 20.20.1affected · semver
    • 22.22.1 and later · up to and including 22.22.1affected · semver
    • 24.14.0 and later · up to and including 24.14.0affected · semver
    • 25.8.1 and later · up to and including 25.8.1affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10nodejs24-docsbefore 1:24.14.1-2.el10_11:24.14.1-2.el10_1
AlmaLinux:10nodejs24-npmbefore 1:11.11.0-1.24.14.1.2.el10_11:11.11.0-1.24.14.1.2.el10_1
AlmaLinux:8nodejsbefore 1:24.14.1-2.module_el8.10.0+4160+4819ac421:24.14.1-2.module_el8.10.0+4160+4819ac42
AlmaLinux:8nodejs-develbefore 1:24.14.1-2.module_el8.10.0+4160+4819ac421:24.14.1-2.module_el8.10.0+4160+4819ac42
AlmaLinux:8nodejs-docsbefore 1:24.14.1-2.module_el8.10.0+4160+4819ac421:24.14.1-2.module_el8.10.0+4160+4819ac42
AlmaLinux:8nodejs-full-i18nbefore 1:24.14.1-2.module_el8.10.0+4160+4819ac421:24.14.1-2.module_el8.10.0+4160+4819ac42
AlmaLinux:8nodejs-libsbefore 1:24.14.1-2.module_el8.10.0+4160+4819ac421:24.14.1-2.module_el8.10.0+4160+4819ac42
AlmaLinux:8nodejs-nodemonbefore 3.0.3-1.module_el8.10.0+4061+f8ceeab93.0.3-1.module_el8.10.0+4061+f8ceeab9
AlmaLinux:8nodejs-packagingbefore 2021.06-6.module_el8.10.0+4086+70facd4a2021.06-6.module_el8.10.0+4086+70facd4a
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-6.module_el8.10.0+4086+70facd4a2021.06-6.module_el8.10.0+4086+70facd4a
AlmaLinux:8npmbefore 1:11.11.0-1.24.14.1.2.module_el8.10.0+4160+4819ac421:11.11.0-1.24.14.1.2.module_el8.10.0+4160+4819ac42
AlmaLinux:8v8-13.6-develbefore 3:13.6.233.17-1.24.14.1.2.module_el8.10.0+4160+4819ac423:13.6.233.17-1.24.14.1.2.module_el8.10.0+4160+4819ac42
AlmaLinux:9nodejsbefore 1:24.14.1-2.module_el9.7.0+222+ef1c61e11:24.14.1-2.module_el9.7.0+222+ef1c61e1
AlmaLinux:9nodejs-develbefore 1:24.14.1-2.module_el9.7.0+222+ef1c61e11:24.14.1-2.module_el9.7.0+222+ef1c61e1
AlmaLinux:9nodejs-docsbefore 1:24.14.1-2.module_el9.7.0+222+ef1c61e11:24.14.1-2.module_el9.7.0+222+ef1c61e1
AlmaLinux:9nodejs-full-i18nbefore 1:24.14.1-2.module_el9.7.0+222+ef1c61e11:24.14.1-2.module_el9.7.0+222+ef1c61e1
AlmaLinux:9nodejs-libsbefore 1:24.14.1-2.module_el9.7.0+222+ef1c61e11:24.14.1-2.module_el9.7.0+222+ef1c61e1
AlmaLinux:9nodejs-nodemonbefore 3.0.3-3.module_el9.7.0+209+ecf6523e3.0.3-3.module_el9.7.0+209+ecf6523e
AlmaLinux:9nodejs-packagingbefore 2021.06-6.module_el9.7.0+209+ecf6523e2021.06-6.module_el9.7.0+209+ecf6523e
AlmaLinux:9nodejs-packaging-bundlerbefore 2021.06-6.module_el9.7.0+198+8bf605ba2021.06-6.module_el9.7.0+198+8bf605ba
AlmaLinux:9npmbefore 1:11.11.0-1.24.14.1.2.module_el9.7.0+222+ef1c61e11:11.11.0-1.24.14.1.2.module_el9.7.0+222+ef1c61e1
AlmaLinux:9v8-13.6-develbefore 3:13.6.233.17-1.24.14.1.2.module_el9.7.0+222+ef1c61e13:13.6.233.17-1.24.14.1.2.module_el9.7.0+222+ef1c61e1
Alpine:v3.21nodejsbefore 22.22.2-r022.22.2-r0
Alpine:v3.23nodejsbefore 24.14.1-r024.14.1-r0

+84

Same product

nodejs: all records

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-2026-21714Mar 30, 2026 · A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOW_UPDATE frames on stream 0 (connection-level) that cause the flow c
    21Monitor
  • ← EarlierCVE-2026-21715Mar 30, 2026 · A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync.native()` without the required read permission checks, whi
    13Monitor
  • Later →CVE-2026-21717Mar 30, 2026 · A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially pr
    23Monitor

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
azl3 nodejs 20.14.0-14 on Azure Linux 3.020.14.0-15 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 nodejs24 24.13.0-3 on Azure Linux 3.024.14.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:nodejs1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-devel1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-docs1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-full-i18n1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-libs1:24.14.1-2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-nodemon3.0.3-3.module_el9.7.0+209+ecf6523e · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-packaging2021.06-6.module_el9.7.0+209+ecf6523e · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-packaging-bundler2021.06-6.module_el9.7.0+198+8bf605ba · AlmaLinux:9Package registry (OSV)
almalinux:nodejs24-docs1:24.14.1-2.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-npm1:11.11.0-1.24.14.1.2.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:npm1:11.11.0-1.24.14.1.2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9Package registry (OSV)
almalinux:v8-13.6-devel3:13.6.233.17-1.24.14.1.2.module_el9.7.0+222+ef1c61e1 · AlmaLinux:9Package registry (OSV)
alpine:nodejs22.22.2-r0 · Alpine:v3.21Package registry (OSV)
debian:nodejs20.19.2+dfsg-1+deb13u2 · Debian:13Package registry (OSV)
opensuse:nodejs2222.23.0-160000.1.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:nodejs2424.14.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:nodejs1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-debuginfo1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-debugsource1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-devel1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-docs1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-full-i18n1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-libs1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-libs-debuginfo1:24.14.1-2.module+el9.7.0+24166+51c9666b · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs240:24.14.1-4.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-bin0:24.14.1-4.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-devel0:24.14.1-4.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-docs0:24.14.1-4.hum1 · Red Hat:hummingbird:1Package registry (OSV)

+14

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.

Credits

All researchers

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.

No nightly-computed relations.

Chain candidates

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

—

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

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

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

Weakness class (CWE)

CWE-862 · Missing Authorization

CVSS vector

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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.

Change log

  1. Fix✗ → ✓

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

References

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

All records