Home/CVE/A flaw in Node.js Permission API can cause a local server to be started (via a Unix domain socket), even without the `--
CVE

CVE-2026-48936

A flaw in Node.js Permission API can cause a local server to be started (via a Unix domain socket), even without the `--

A flaw in Node.js Permission API can cause a local server to be started (via a Unix domain socket), even without the --allow-net permission. This vulnerability affects one supported release line: Node.js 26.

LOW · CVSS 3.3 EPSS 0.00149
EPSS exploitation odds0.15% · top 95%
Monitor
  • No active-exploitation, high-EPSS, or public-exploit signals - routine patching cadence
Look this up elsewhere - one-click external pivots
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-48936, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

Severity & exploitation scoring

View on NVD →
CVSS base score
3.3
LOWCVSS v3.0 · [email protected]
EPSS exploitation probability
0.15%
Top 95%odds of exploitation in the next 30 days
CVSS metric silhouette
VectorComplexityPrivilegesInteractionScopeConfidentialityIntegrityAvailability
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
no
Tech impact
partial
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Impact - what breaks
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
VECTORCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

ATT&CK techniques

1

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small marks a technique that N independent sources agree on.

▤ Build a SIEM detection for these techniques

Weakness Classification

📦

Fixed versions by distribution

36
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15nodejs10 open
suse sle15nodejs10-devel open
suse sle15nodejs10-docs open
suse sle15nodejs12 open
suse sle15nodejs12-devel open
suse sle15nodejs12-docs open
suse sle15nodejs14 open
suse sle15nodejs14-devel open
suse sle15nodejs14-docs open
suse sle15nodejs16 open
suse sle15nodejs16-devel open
suse sle15nodejs16-docs open
suse sle15nodejs18 open
suse sle15nodejs18-devel open
suse sle15nodejs18-docs open
suse sle15nodejs20 open
suse sle15nodejs20-devel open
suse sle15nodejs20-docs open
suse sle15nodejs22 open
suse sle15nodejs22-devel open
suse sle15nodejs22-docs open
suse sle15nodejs24 open
suse sle15nodejs24-devel open
suse sle15nodejs24-docs open
suse sle15nodejs8 open
suse sle15nodejs8-devel open
suse sle15nodejs8-docs open
suse sle15npm10 open
suse sle15npm12 open
suse sle15npm14 open
suse sle15npm16 open
suse sle15npm18 open
suse sle15npm20 open
suse sle15npm22 open
suse sle15npm24 open
suse sle15npm8 open

Vendor Advisories

1
🔗

References & Sources

1
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.