CVE-2026-75518
DOMShell read-only eval could change browser state
apireno · DOMShell
First documented disclosure · Review checkpoint
Summary
A caller denied write access could still execute side-effecting JavaScript through eval.
Severity and exploitation evidence
Medium · 4.8/10 · CVSS 4.0. Severity source.
Exploitation not established: Malicious exploitation remains unverified in the reviewed originals. A demonstration or absence from KEV does not establish exploitation status.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The eval tool was placed in the read tier although it shared the unrestricted JavaScript execution handler.
Conditions required
MCP tool-session access without --allow-write.
Potential impact
Browser DOM, window or global state can change while approval interfaces and logs describe the operation as read-only.
Affected versions and configurations
DOMShell: < 2.0.8.
Fix and mitigation status
2.0.8 of the MCP server; the browser extension is unchanged.
Practical next steps
Apply the issue-specific correction: 2.0.8 of the MCP server; the browser extension is unchanged. Restrict the affected tool or endpoint until the correction is deployed.
Operating lesson
Match tool annotations and approval tiers to actual capabilities.
Evidence and limits
Earliest reviewed public evidence 2026-07-08; CVE publication 2026-11-18. CVSS 4.0 4.8 is attributed to GitHub_M in the CNA record.
Sources
- GitHub_M CVE authority record
Primary source ·
- Maintainer security advisory
Primary source ·
- Original correction or vendor bulletin
Primary source ·