Medium

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

  • Disclosed: 19.11.2026
  • Updated: 20.11.2026 10:00

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 the actual agency being granted to an AI agent.

Affected code paths

  • mcp-server/index.ts:113 — WRITE_COMMANDS excluded eval
  • mcp-server/index.ts:879-887 — domshell_eval registered with ANNO_READ and description asserting read-only
  • src/background/index.ts:1849-1854 — js and eval both dispatch to handleJs(rawCode)
  • src/background/index.ts:3282 — handleJs calls cdp.evaluateJs(code)
  • src/background/cdp_client.ts:660-667 — evaluateJs sends Runtime.evaluate with expression: code, returnByValue: true, awaitPromise: true and no throwOnSideEffect gate

Fix

Shipped in @apireno/domshell@2.0.8 (2026-07-08):

  • eval added to WRITE_COMMANDS, aligning tier with actual capability
  • domshell_eval MCP annotation changed from ANNO_READ to ANNO_WRITE
  • Tool description and MCP_INSTRUCTIONS updated to remove read-only language; read-only DOM inspection needs pointed at domshell_cat / domshell_text / domshell_find
  • Server-only patch — no Chrome Web Store submission required; extension code unchanged
  • SECURITY.md added + GitHub Private Vulnerability Reporting enabled on the repo

Upgrade path

bash
npm install @apireno/domshell@2.0.8

Or, in a persistent install, restart your MCP server against the new version.

Drives that call eval without --allow-write will start receiving Error: 'eval' requires --allow-write. Options:

  • Add --allow-write to the server flags if eval's write capability is actually needed
  • Migrate read-only inspection to domshell_cat / domshell_text / domshell_find
  • Migrate to domshell_js if the caller already runs with --allow-write (same tier, same capability)

Integrator impact

  • HKUDS/CLI-Anything — unaffected; their harness doesn't invoke eval or js commands (verified by grep).
  • Kgspin QA-UX drives — unaffected; they run with --allow-write for their action gates.
  • Direct Claude Desktop / Cursor sessions — any that called domshell_eval without --allow-write will now be denied, aligning behavior with the documented contract.

Reporter / Credit

Ugur Ozer, AI Risk Management https://airiskmanagement.ca info@airiskmanagement.ca

Source-review-first responsible disclosure via private email to the maintainer on 2026-07-08. Reporter finding id: DOMSHELL-EVAL-READ-TIER-BYPASS-001. Ugur followed the standard disclosure ladder correctly despite the missing SECURITY.md at time of report — that gap has now been closed (repo now has SECURITY.md + GitHub Private Vulnerability Reporting enabled).

Timeline

  • 2026-07-08 — Report received by maintainer via private email
  • 2026-07-08 — Source-side claims verified against main at 2d63dab; fix planned
  • 2026-07-08 — @apireno/domshell@2.0.8 released to npm and the MCP registry; SECURITY.md added; GitHub PVR enabled
  • 2026-07-08 — This advisory published

What to do

Upgrade to @apireno/domshell@2.0.8 (2026-07-08):

bash

npm install @apireno/domshell@2.0.8

Or, in a persistent install, restart the MCP server against the new version.

Callers invoking eval without --allow-write will start receiving Error: 'eval' requires --allow-write. Options:

  • Add --allow-write to the server flags if eval's write capability is actually needed
  • Migrate read-only inspection to domshell_cat / domshell_text / domshell_find
  • Migrate to domshell_js if the caller already runs with --allow-write (same tier, same capability)

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package @apireno/domshell < 2.0.8 2.0.8

References

CVSS score -
CVSS vector
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
Weakness (CWE)
CWE-266, CWE-863
Platform
npm
Package
@apireno/domshell
Disclosed
19.11.2026
Updated
20.11.2026 10:00

Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.

OSV / GitHub Advisory Database - GHSA-vg83-hcp4-5qcc - CC BY 4.0

Vulnerability history: @apireno/domshell

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

This is the only known vulnerability of this package.

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.