cve.bz

CVE-2026-75518 DOMShell: domshell_eval classified as read-tier can execute side-effecting JavaScript without --allow-write

4.8 mediumEPSS 0.1%Fix available

Medium (4.8) in apireno domshell. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in @apireno/domshell 2.0.8.

On this page
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.

Severity

CVSS 4.0

4.8 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-266 Incorrect Privilege Assignment
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • @apireno/domshell (npm): fixed in 2.0.8

Ask an AI about this CVE

Show the promptExplain CVE-2026-75518 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-75518?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-75518?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-75518 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
apireno DOMShell< 2.0.8

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vg83-hcp4-5qccnpm@apireno/domshell<2.0.82.0.8

References

Check your stackJSON