Siemens Mendix Studio Pro flaws expose its MCP Server to remote and browser-based attacks
CISA has published an advisory on two vulnerabilities in the MCP Server component of Siemens Mendix Studio Pro, a development tool used to build business applications. The issues carry a CVSS v3 score of 8.8 (high) and could lead to unauthorised data access, tool execution or system compromise.
The first flaw, CVE-2026-112136, is that the MCP Server does not properly restrict its HTTP listener to the loopback interface. This means it may be reachable from other systems, so an attacker with network access could interact with it remotely.
The second flaw, CVE-2026-112137, is a cross-site request forgery weakness. The server does not properly check Content-Type and Origin headers on incoming requests. A malicious web page could therefore trick a user's browser into sending unauthorised requests and triggering unintended actions on the local server.
Affected versions are Mendix Studio Pro 11 from 11.15.0 up to but not including 11.16.0, and the 11.12 branch from 11.12.6 up to but not including 11.12.7. Siemens has released fixed versions (11.16.0 and 11.12.7 or later) and recommends updating. Where patching is delayed, the advisory suggests blocking external traffic to port 7782 with a firewall (the default on standard Windows installations), and using a VPN or SSH tunnel if remote access is needed. For the browser-based issue, it suggests modern Chromium or WebKit browsers with Private Network Access protections, or extensions that stop external sites making requests to localhost.
Why it matters
Developer workstations running local tooling are often treated as trusted and outside the network perimeter, but this advisory shows a local service can be reached from the network or from a web page in the developer's own browser. Teams using Mendix are exposed, particularly where developers browse the web on the same machine that runs Studio Pro. It forces a decision to treat local developer services as attack surface and check their listening addresses and firewall rules.
What to do
- Update Mendix Studio Pro 11 to V11.16.0 or later, or the 11.12 branch to V11.12.7 or later.
- Block inbound external traffic to port 7782 with Windows Defender Firewall or an equivalent.
- Use a VPN or SSH tunnel instead of opening direct firewall rules if remote access is required.
- Use modern browsers with Private Network Access protections enabled on developer machines.