CVE-2026-75518: apireno DOMShell · Incorrect Privilege Assignment
Affects apireno DOMShellSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium : upgrade to 2.0.8 when convenient.
Data as of 18 Nov 2026, 22:04 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 4.8 |
|---|
- Patch
- Available – fixed in 2.0.8
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade apireno DOMShell to 2.0.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| apirenoDOMShell | Affected
| Fixed in
|
Description
DOMShell is a Chrome automation project whose MCP server exposes Unix-style tools for AI agents. Prior to 2.0.8, the DOMShell MCP server classifies the domshell_eval tool and eval command as read-tier operations that can run without --allow-write, even though eval shares the Runtime.evaluate dispatch path with the write-tier js command and has no side-effect gate. An MCP caller with tool-session access can therefore use domshell_eval to mutate DOM, window, or global state while the host approval interface, server authorization flags, denial messages, and audit records represent the operation as read-only. The bypass does not expose a capability beyond domshell_js for callers already authorized to write, but it violates the configured permission boundary for callers lacking that authorization. This issue is fixed in version 2.0.8.