← All advisories
CVE-2026-75518mediumAgent hijacking2026-11-19

Browser-automation MCP servers broke their read-only modes: Safari MCP read-only tools could run arbitrary page JavaScript via an escaping bug (fixed 2.22.15), and DOMShell's domshell_eval ran writes without --allow-write (CVE-2026-75518, fixed 2.0.8)

Two MCP servers that let AI agents drive a real browser promised a read-only tier that didn't hold. Safari MCP (npm safari-mcp) put tool arguments inside single-quoted JavaScript strings in 16 places and escaped the quote but not backslashes, so an argument with a backslash and a quote broke out and ran as page JavaScript. Seven of those arguments belong to read-only tools exempt from the tab-ownership check, so a client limited to read-only tools (safari_evaluate and safari_run_script excluded) could still run arbitrary JavaScript, even in tabs the session doesn't own (fixed 2.22.15). DOMShell (npm @apireno/domshell) classified domshell_eval as read-tier although it shares the Runtime.evaluate path with the write-tier js command, so it could mutate the page without --allow-write while MCP hosts showed a read-only approval UI (CVE-2026-75518, fixed 2.0.8).

01.

What it is

Safari MCP (GHSA-4rj4-rcrq-gr92, no CVE): affected read-only arguments are filter in safari_network_details and safari_extract_links, level in safari_console_filter, selector in safari_snapshot, safari_accessibility_snapshot and safari_extract_tables, and dbName/storeName in safari_get_indexed_db. Other affected arguments include ref in safari_select_option, the key in safari_press_key and file names in safari_upload_file / safari_paste_image. The fix routes every site through a shared escJsSingleQuote helper. Affected: safari-mcp < 2.22.15 (released 10 October 2026); the advisory reached the GitHub Advisory Database on 19 November 2026. There is no configuration workaround.

DOMShell (GHSA-vg83-hcp4-5qcc, CVE-2026-75518): the tool advertised readOnlyHint: true, so hosts such as Claude Desktop and Cursor rendered the wrong approval UI, and audit logs labelled write activity as read. It exposes nothing beyond what domshell_js already allows with --allow-write. Affected: @apireno/domshell < 2.0.8; NVD published the CVE on 18 November 2026.

In both cases, text the agent reads from a web page or other untrusted source can steer the arguments it passes, so a 'read-only' allowlist was not a real boundary.

02.

How to check

  1. npm ls -g safari-mcp @apireno/domshell, or check the version pinned in your MCP client config (npx/uvx args).
  2. Check whether you relied on read-only tool allowlists or on running DOMShell without --allow-write.
03.

How to fix

  1. Upgrade safari-mcp to 2.22.15 or later and @apireno/domshell (MCP) to 2.0.8 or later.
  2. Use a separate browser profile for agent automation, without your logged-in sessions.
npm ls -g safari-mcp @apireno/domshell 2>/dev/null
grep -rnE 'safari-mcp|domshell' ~/.cursor/mcp.json ~/Library/Application\ Support/Claude/claude_desktop_config.json 2>/dev/null
04.

Sources

More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.