Siemens Mendix Studio Pro: two MCP Server flaws fixed in new releases
Siemens and CISA disclosed two vulnerabilities in the MCP Server of Mendix Studio Pro: an HTTP listener bound beyond the loopback interface and a cross-site request forgery issue. Development teams running affected 11 and 11.12 releases are concerned, with critical manufacturing and energy listed among the sectors.
What to do now
- Product
- Siemens Mendix Studio Pro
- Affected versions
- Mendix Studio Pro 11: >= 11.15.0 and < 11.16.0; Mendix Studio Pro 11.12: >= 11.12.6 and < 11.12.7
- Fixed in
- 11.16.0 or later (11 branch); 11.12 branch: 11.12.7 falls outside the affected range
- CVE
- CVE-2026-112136
CISA has issued an advisory covering Mendix Studio Pro, Siemens' low-code development environment. It describes two vulnerabilities, CVE-2026-112136 and CVE-2026-112137, in the MCP Server built into the product.
CVE-2026-112136 stems from the MCP Server's HTTP listener. It is not properly restricted to the loopback interface, so it may be reachable from remote systems. An attacker with network access could then interact with the server remotely.
CVE-2026-112137 is a cross-site request forgery weakness. An attacker could trick a user's browser into sending unauthorized requests to the server. According to the advisory, the two flaws could lead to unauthorized data access, tool execution or full system compromise.
Two version ranges are affected: Mendix Studio Pro 11 from 11.15.0 up to but not including 11.16.0, and Mendix Studio Pro 11.12 from 11.12.6 up to but not including 11.12.7. Siemens has released new versions and recommends updating to the latest ones. For the 11 branch, the fix is version 11.16.0 or later. The available advisory text is cut off before the 11.12 remediation. However, the stated range places 11.12.7 outside the affected versions.
As a mitigation, Siemens advises strict inbound firewall policies, such as Windows Defender Firewall, that block external traffic on port 7782. The vendor notes this is already the default on standard Windows installations. Where remote access is required, it should go through a secure, authenticated channel such as a VPN or SSH tunnel rather than a direct inbound firewall rule.
What to do now
- Update Mendix Studio Pro 11 to version 11.16.0 or later, and move 11.12 installations out of the 11.12.6 to pre-11.12.7 range.
- Confirm that host firewalls on developer workstations block external inbound traffic on port 7782.
- Remove any direct inbound rule exposing port 7782 and use a VPN or SSH tunnel if remote access is truly needed.
- Inventory machines running Mendix Studio Pro to identify those on affected versions.