CVE
DOMShell privilege escalation in MCP server's read-tier eval tool
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.8
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.0.8.
Summary
DOMShell, a Chrome automation project whose MCP server exposes tools for AI agents, has a permission bypass in its domshell_eval tool, which is classified as read-only and can run without the write flag. A local caller with low-privilege access to the tool session can use it to change page DOM, window, or global state that the write restriction was meant to block, while approval prompts, logs, and denial messages show the action as read-only.
Original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.8/10CVSS 4.8
- No patch0/5No signal
What would change the score
- Would score about 60 if added to CISA KEV
- Would score about 55 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.0.8.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-75518 (DOMShell: domshell_eval classified as read-tier can execute side-effecting JavaScript without --allow-write), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-75518 (entry last updated 2026-11-18):
Affected:
- apireno DOMShell: fixed in 2.0.8
Fixed versions: 2.0.8.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-75518 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-75518 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/apireno/DOMShell/security/advisories/GHSA-vg83-hcp4-5qcc
- https://github.com/apireno/DOMShell/commit/03c1d7625e220297aff0dde37613d65cfe6f9a36
- https://github.com/apireno/DOMShell/releases/tag/mcp-v2.0.8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-75518
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-75518"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- apireno DOMShell
fixed in 2.0.8
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · apireno/DOMShell · Advisory GHSA-vg83-hcp4-5qcc |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-75518 |
| Record | NVD · CVE-2026-75518 |
| Other links 2 | |
| Repository | GitHub · apireno/DOMShell · Commit 03c1d762 |
| Repository | GitHub · apireno/DOMShell · Release mcp-v2.0.8 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-75518
Is CVE-2026-75518 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-75518?
DOMShell: before 2.0.8.Source: cve.now feed data
How do I fix CVE-2026-75518?
Upgrade to a fixed version: 2.0.8.Source: cve.now feed data