Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to vulnerabilities
Unrated

Node.js Permission Model bypass via FileHandle.utimes() on read-only paths

IdentifiersCVE-2026-48935CWE-284

CVE-2026-48935 is a low-severity vulnerability in Node.js affecting the Permission API / permission model. According to the provided content, the flaw allows file metadata to be modified on a path that was configured as read-only, including when access restrictions are enforced with flags such as --allow-fs-read. The issue is specifically described as a permission model bypass via FileHandle.utimes() in the Promises API, enabling timestamp or related file metadata changes on paths that should be restricted to read-only access.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to bypass Node.js filesystem permission restrictions and modify file metadata on paths that were intended to be read-only. This undermines the integrity guarantees of the permission model and can permit unauthorized alteration of file timestamps or similar metadata on otherwise restricted files.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, avoid relying on the Node.js permission model alone to enforce filesystem write restrictions for sensitive paths. Restrict execution of untrusted Node.js code, use OS-level filesystem permissions and sandboxing to enforce read-only access, and disable or avoid exposing code paths that can obtain and use FileHandle.utimes() against sensitive files until patched.

Remediation

Patch, then assume compromise.

Upgrade Node.js to a fixed release. The provided content identifies the patched versions as Node.js v22.23.0, v24.17.0, and v26.3.1, with later reporting also referencing patched versions v22.23.1, v24.17.1, and v26.3.2. Use the latest available patched release in the affected major line.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

5 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-48935
NVD
nvd.nist.gov/vuln/detail/CVE-2026-48935
MITRE CWE · CWE-284
cwe.mitre.org