DOMShell: domshell_eval classified as read-tier can execute side-effecting JavaScript without --allow-writeGHSA-vg83-hcp4-5qcc
Fix: apireno/DOMShell@03c1d76GHSA-vg83-hcp4-5qcc is a CWE-266 vulnerability in @apireno/domshell. A fix is available for @apireno/domshell — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
@apireno/domshellReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
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
evalcall
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_COMMANDSexcludedevalmcp-server/index.ts:879-887—domshell_evalregistered withANNO_READand description asserting read-onlysrc/background/index.ts:1849-1854—jsandevalboth dispatch tohandleJs(rawCode)src/background/index.ts:3282—handleJscallscdp.evaluateJs(code)src/background/cdp_client.ts:660-667—evaluateJssendsRuntime.evaluatewithexpression: code, returnByValue: true, awaitPromise: trueand nothrowOnSideEffectgate
Fix
Shipped in @apireno/[email protected] (2026-07-08):
evaladded toWRITE_COMMANDS, aligning tier with actual capabilitydomshell_evalMCP annotation changed fromANNO_READtoANNO_WRITE- Tool description and
MCP_INSTRUCTIONSupdated to remove read-only language; read-only DOM inspection needs pointed atdomshell_cat/domshell_text/domshell_find - Server-only patch — no Chrome Web Store submission required; extension code unchanged
SECURITY.mdadded + GitHub Private Vulnerability Reporting enabled on the repo
Upgrade path
npm install @apireno/[email protected]
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-writeto the server flags ifeval's write capability is actually needed - Migrate read-only inspection to
domshell_cat/domshell_text/domshell_find - Migrate to
domshell_jsif the caller already runs with--allow-write(same tier, same capability)
Integrator impact
- HKUDS/CLI-Anything — unaffected; their harness doesn't invoke
evalorjscommands (verified by grep). - Kgspin QA-UX drives — unaffected; they run with
--allow-writefor their action gates. - Direct Claude Desktop / Cursor sessions — any that called
domshell_evalwithout--allow-writewill now be denied, aligning behavior with the documented contract.
Reporter / Credit
Ugur Ozer, AI Risk Management https://airiskmanagement.ca [email protected]
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
mainat2d63dab; fix planned - 2026-07-08 —
@apireno/[email protected]released to npm and the MCP registry;SECURITY.mdadded; GitHub PVR enabled - 2026-07-08 — This advisory published
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @apireno/domshell | all versions | 2.0.8npm install @apireno/domshell@2.0.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @apireno/domshell, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @apireno/domshell to 2.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vg83-hcp4-5qcc is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-vg83-hcp4-5qcc in your dependencies?
Find it across npm, including transitive dependencies.