Home/Research/Post

GHSA-vg83-hcp4-5qcc: DOMShell: domshell_eval classified as read-tier can execute side-effecting JavaScript without –allow-write

  • Severity: MEDIUM
  • CVE: CVE-2026-75518
  • Ecosystems: npm
  • Packages: @apireno/domshell

### Summary

The `domshell_eval` MCP tool (and the `eval` command inside `domshell_execute`) was classified as **read-tier**, allowing it to run without the `–allow-write` server flag. However, `eval` and the write-tier `js` command dispatch to the same handler in the extension and call CDP `Runtime.evaluate` with the raw expression string and no side-effect gate. Any JavaScript expression could therefore mutate DOM, window, or global state through `domshell_eval` without the operator’s `–allow-write` authorization.

The tool description explicitly promised “(read-only) … always available in read-only mode” — the misclassification contradicted the documented contract, not just an implicit one.

### Impact

No new capability was exposed — the same write access was already available via `domshell_js` with `–allow-write` — but the tier misclassification meant:

– MCP hosts (Claude Desktop, Cursor, etc.) rendered the wrong approval UI (`readOnlyHint: true`)
– Server-side tier flags (`–allow-write`) misrepresented what an AI agent was actually authorized to do
– Audit logs and deny messages labeled write-tier activity as read-tier
– Downstream tools and analysis relying on the tier separation could over-trust an `eval` call

Framing: OWASP LLM Top 10 LLM06 (Excessive Agency), NIST AI RMF (tool permission boundary + human-approval fidelity), CWE-863 (Incorrect Authorization).

The reporter’s main framing: **the MCP approval UI and server-side permission model can misrepresent…

Source: GitHub Security Advisories · 2026-11-19