Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-48617: A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalida

40
This month
HIGH 8.2REMOTEUPGRADE

CVE-2026-48617 is a high-severity flaw (CVSS 8.2) affecting node.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score8.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.3% (top 76%)
CISA exploited listNo
WeaknessCWE-284
Published2026-06-18
Last modified2026-10-26
Publisher (CNA): HackerOne · Vendor: nodejs

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

nodejs node.js UPGRADE
Affected: >= 22.0.0 and <= 22.22.3 · >= 24.0.0 and <= 24.16.0 · >= 26.0.0 and <= 26.3.0
Fixed in: newer than 26.3.0
Safe to downgrade to: a release before 22.0.0
1. Check installed version
apt-cache policy node.js || rpm -q node.js || node.js --version
2. UPGRADE to newer than 26.3.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade node.js
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade node.js
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 22.0.0 (Debian / Ubuntu)
apt-cache madison node.js sudo apt install node.js=<VERSION_BEFORE_22.0.0> sudo apt-mark hold node.js
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list node.js sudo dnf downgrade node.js-<VERSION_BEFORE_22.0.0> sudo dnf versionlock add node.js
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-48617?

node.js: upgrade to newer than 26.3.0. Exact commands for each OS are on this page.

Is CVE-2026-48617 being exploited?

CVE-2026-48617 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-48617 affect?

CVE-2026-48617 affects node.js. Severity is high (CVSS 8.2). A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vuln

How urgent is CVE-2026-48617?

Priority 40/100. High severity; Remotely exploitable, no login, no user action

Software pages

Node.js vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.