Is there a public exploit for CVE-2026-106073?

Yes. Proof-of-concept code for CVE-2026-106073 has been published publicly.

Is there a proof of concept for CVE-2026-106073?

Yes — 1 proof-of-concept entry is linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2026-106073?

CVE-2026-106073 scores CVSS 3.3 (v3.0), rated low. EPSS puts the chance of exploitation in the next 30 days at 0.25%.

What does CVE-2026-106073 affect?

CVE-2026-106073 affects nodejs Node.

3.3 Low

A flaw in Node.js Permission Model filesystem enforcement leaves fs.realpathSync() without the required read permission checks.

CVE-2026-106073

A flaw in Node.js Permission Model filesystem enforcement leaves fs.realpathSync() without the required read permission checks. This is an incomplete fix of CVE-2026-21715, which only covered fs.realpathSync.native(). As a result, code running under --permission with restricted --allow-fs-read can still use fs.realpathSync() to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Proof-of-concept code is published

Public PoC

Public PoCCompleteTech-Security/node-cve-2026-106073-check

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Assessment

CVSS: 3.3 (v3.0)
Severity: Low
EPSS: 0.25% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Public PoC
Published: 23 October 2026
Last updated: 2 November 2026
Affected: nodejs · Node
Assigner: hackerone

CVSS vectorCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

At the source

EUVD (ENISA)

References

https://nodejs.org/en/blog/vulnerability/october-2026-security-releases

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 8 + 6? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-106073