CVE-2026-75518apireno DOMShell incorrect privilege assignment
CVE-2026-75518 is a incorrect privilege assignment in apireno DOMShell, rated medium (4.8 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
A user or process is given privileges it should not have. A permission check exists but gets the answer wrong for some callers.
How it is reached
An attacker can exploit it by someone who can already run code or sign in on the machine, with an ordinary user account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker reach data or actions their role should not allow.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade apireno DOMShell to 2.0.8 or later.
- Limit who can run code or sign in on the hosts that run it.
Description from NVD
DOMShell is a Chrome automation project whose MCP server exposes Unix-style tools for AI agents. Prior to 2.0.8, the DOMShell MCP server classifies the domshell_eval tool and eval command as read-tier operations that can run without --allow-write, even though eval shares the Runtime.evaluate dispatch path with the write-tier js command and has no side-effect gate. An MCP caller with tool-session access can therefore use domshell_eval to mutate DOM, window, or global state while the host approval interface, server authorization flags, denial messages, and audit records represent the operation as read-only. The bypass does not expose a capability beyond domshell_js for callers already authorized to write, but it violates the configured permission boundary for callers lacking that authorization. This issue is fixed in version 2.0.8.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
- Multi-tenant services. The flaw sits between one role or tenant and another.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.
Questions to answer about your own systems
- Where does apireno DOMShell run in your systems, and at which version?
- Which of those hosts also run code or users you do not fully trust?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.