{"id":"CVE-2026-75518","aliases":["GHSA-vg83-hcp4-5qcc"],"url":"https://o3.security/vulnerability/CVE-2026-75518","summary":"DOMShell: domshell_eval classified as read-tier can execute side-effecting JavaScript without --allow-write","details":"### Summary\n\nThe `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.\n\nThe tool description explicitly promised \"(read-only) ... always available in read-only mode\" — the misclassification contradicted the documented contract, not just an implicit one.\n\n### Impact\n\nNo new capability was exposed — the same write access was already available via `domshell_js` with `--allow-write` — but the tier misclassification meant:\n\n- MCP hosts (Claude Desktop, Cursor, etc.) rendered the wrong approval UI (`readOnlyHint: true`)\n- Server-side tier flags (`--allow-write`) misrepresented what an AI agent was actually authorized to do\n- Audit logs and deny messages labeled write-tier activity as read-tier\n- Downstream tools and analysis relying on the tier separation could over-trust an `eval` call\n\nFraming: OWASP LLM Top 10 LLM06 (Excessive Agency), NIST AI RMF (tool permission boundary + human-approval fidelity), CWE-863 (Incorrect Authorization).\n\nThe reporter's main framing: **the MCP approval UI and server-side permission model can misrepresent the actual agency being granted to an AI agent.**\n\n### Affected code paths\n\n- `mcp-server/index.ts:113` — `WRITE_COMMANDS` excluded `eval`\n- `mcp-server/index.ts:879-887` — `domshell_eval` registered with `ANNO_READ` and description asserting read-only\n- `src/background/index.ts:1849-1854` — `js` and `eval` both dispatch to `handleJs(rawCode)`\n- `src/background/index.ts:3282` — `handleJs` calls `cdp.evaluateJs(code)`\n- `src/background/cdp_client.ts:660-667` — `evaluateJs` sends `Runtime.evaluate` with `expression: code, returnByValue: true, awaitPromise: true` and no `throwOnSideEffect` gate\n\n### Fix\n\nShipped in `@apireno/domshell@2.0.8` (2026-07-08):\n\n- `eval` added to `WRITE_COMMANDS`, aligning tier with actual capability\n- `domshell_eval` MCP annotation changed from `ANNO_READ` to `ANNO_WRITE`\n- Tool description and `MCP_INSTRUCTIONS` updated to remove read-only language; read-only DOM inspection needs pointed at `domshell_cat` / `domshell_text` / `domshell_find`\n- Server-only patch — no Chrome Web Store submission required; extension code unchanged\n- `SECURITY.md` added + GitHub Private Vulnerability Reporting enabled on the repo\n\n### Upgrade path\n\n```\nnpm install @apireno/domshell@2.0.8\n```\n\nOr, in a persistent install, restart your MCP server against the new version.\n\nDrives that call `eval` without `--allow-write` will start receiving `Error: 'eval' requires --allow-write`. Options:\n\n- Add `--allow-write` to the server flags if `eval`'s write capability is actually needed\n- Migrate read-only inspection to `domshell_cat` / `domshell_text` / `domshell_find`\n- Migrate to `domshell_js` if the caller already runs with `--allow-write` (same tier, same capability)\n\n### Integrator impact\n\n- **HKUDS/CLI-Anything** — unaffected; their harness doesn't invoke `eval` or `js` commands (verified by grep).\n- **Kgspin QA-UX drives** — unaffected; they run with `--allow-write` for their action gates.\n- **Direct Claude Desktop / Cursor sessions** — any that called `domshell_eval` without `--allow-write` will now be denied, aligning behavior with the documented contract.\n\n### Reporter / Credit\n\n**Ugur Ozer, AI Risk Management**\n<https://airiskmanagement.ca>\n<info@airiskmanagement.ca>\n\nSource-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).\n\n### Timeline\n\n- 2026-07-08 — Report received by maintainer via private email\n- 2026-07-08 — Source-side claims verified against `main` at `2d63dab`; fix planned\n- 2026-07-08 — `@apireno/domshell@2.0.8` released to npm and the MCP registry; `SECURITY.md` added; GitHub PVR enabled\n- 2026-07-08 — This advisory published","published":"2026-11-18T21:46:59.857Z","modified":"2026-11-19T21:01:50.683842839Z","cvss":null,"epss":{"score":0.00109,"percentile":0.01252,"asOf":"2026-11-19"},"cisaKev":null,"exploitsKnown":0,"affectedPackages":[{"ecosystem":"npm","name":"@apireno/domshell","fixedVersion":"2.0.8"}],"fix":{"url":"https://github.com/apireno/DOMShell/commit/03c1d7625e220297aff0dde37613d65cfe6f9a36","label":"apireno/DOMShell@03c1d76"},"references":[{"type":"WEB","url":"https://github.com/apireno/DOMShell/releases/tag/mcp-v2.0.8"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/75xxx/CVE-2026-75518.json"},{"type":"ADVISORY","url":"https://github.com/apireno/DOMShell/security/advisories/GHSA-vg83-hcp4-5qcc"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-75518"},{"type":"FIX","url":"https://github.com/apireno/DOMShell/commit/03c1d7625e220297aff0dde37613d65cfe6f9a36"},{"type":"PACKAGE","url":"https://github.com/apireno/DOMShell"}],"provenance":{"sources":["OSV.dev","FIRST.org (EPSS)"],"lastVerified":"2026-11-19T21:01:50.683842839Z"}}