@apireno/domshell · DOMShell: domshell_eval classified as read-tier can execute side-effecting JavaScript without --allow-write
Affects @apireno/domshellSource GCVE Database
Not known to be exploited · CVSS 4.8 Medium : upgrade to 2.0.8 when convenient.
Data as of 19 Nov 2026, 17:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 4.8 |
|---|
- Patch
- Available – fixed in 2.0.8
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade @apireno/domshell to 2.0.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@apireno/domshell | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in @apireno/domshell version 2.0.8, which correctly classifies eval as a write-tier command and enforces the --allow-write flag requirement. Users should upgrade to version 2.0.8 or later. After upgrading, calls to eval without --allow-write will be denied. To maintain read-only inspection, users should migrate to domshell_cat, domshell_text, or domshell_find commands. If eval's write capability is needed, add --allow-write to server flags. No changes to the extension code are required as the fix is server-side only.
Description
The domshell_eval tool in @apireno/domshell was incorrectly classified as read-tier, allowing it to execute JavaScript expressions with side effects without requiring the --allow-write flag. This misclassification contradicted the documented read-only promise and caused UI, permission, and audit log inconsistencies. The issue was fixed in version 2.0.8 by reclassifying eval as a write-tier command and updating the tool description and permission model accordingly.
References
- github.com/apireno/DOMShell/security/advisories/GHSA-vg83-hcp4-5qcc (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-75518 (opens in a new tab)
- github.com/apireno/DOMShell/commit/03c1d7625e220297aff0dde37613d65cfe6f9a36 (opens in a new tab)
- github.com/apireno/DOMShell (opens in a new tab)
- github.com/apireno/DOMShell/releases/tag/mcp-v2.0.8 (opens in a new tab)