Here's the summary for developers and the admins who look after their Windows workstations. You're affected only if you run one of two narrow version ranges. The fix is a normal Studio Pro update, and the interim mitigations are things most Windows shops already have in place.
What Siemens disclosed
According to Siemens, Mendix Studio Pro contains multiple vulnerabilities in the MCP Server, that could allow an attacker with network access to interact with the server remotely or trick a user's browser into sending unauthorized requests, potentially leading to unauthorized data access, tool execution, or system compromise.
Siemens describes these as potential impacts. It does not say anyone has exploited the bugs.
The timeline:
- November 10, 2026: Siemens published SSA-710379 (version 1.0).
- November 16, 2026: The advisory was mapped to Mendix products to be present on the Mendix Atom Feed (version 1.1).
- November 17, 2026: CISA republished it as an ICS advisory.
Mendix's own documentation team moved at the same time. A pull request in the public Mendix docs repository titled "Update Security Advisories for SSA-710379" was merged into the development branch on Nov 10, 2026, so the Mendix security advisories page and the Siemens notice appeared together.
Section summary: This is a vendor-confirmed advisory with two CVEs and published fixes. Nothing indicates the flaws are being exploited.
Affected versions and fixes
Siemens lists two affected ranges, and both contain both CVEs:
| Product line | Affected versions | Fixed version |
|---|---|---|
| Mendix Studio Pro 11 | 11.15.0 up to, but not including, 11.16.0 | 11.16.0 or later |
| Mendix Studio Pro 11.12 | 11.12.6 up to, but not including, 11.12.7 | 11.12.7 or later |
Siemens confirms the ranges: Mendix Studio Pro 11 versions >= V11.15.0 < V11.16.0 and Mendix Studio Pro 11.12 versions >= V11.12.6 < V11.12.7 are affected by CVE-2026-112136 and CVE-2026-112137.
The 11.12 range is very narrow: only 11.12.6 is affected. Teams that stay on the 11.12 line for stability should move to 11.12.7, not jump to the main 11.x stream unless they planned to anyway. Each line has its own fix. Nothing in the advisory suggests that updating one line fixes installations on the other.
Mendix's 11.12 release notes add useful detail. They show that 11.12.7 was released on November 9, 2026, a day before the advisory went public. One entry says Mendix improved Studio Pro MCP Server connection handling. It tells anyone with an MCP client such as Claude Code connected to Studio Pro to disconnect and reconnect it after updating. The release note doesn't name either CVE. The CVE-to-version mapping comes from the Siemens advisory, not the changelog.
Section summary: Update 11.15.x to 11.16.0 or later and 11.12.6 to 11.12.7 or later. Then reconnect your MCP clients.
CVE-2026-112136: the listener wasn't limited to localhost
This is the more serious of the two. In Siemens' words, the affected products MCP Server does not properly restrict its HTTP listener to the loopback interface, leaving it potentially exposed to remote systems. This could allow an attacker with network access to interact with the MCP Server remotely.
Key details:
- CWE: CWE-1327, Binding to an Unrestricted IP Address
- CVSS v3.1: 8.8 (High), vector
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - CVSS v4.0: 9.2, vector
AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
A local MCP server should only accept connections from the same machine. Here's an analogy: you hired a butler to take orders from you alone, but you left the front door unlocked, so anyone walking past can give him orders too. An MCP server for an IDE is designed to let AI tools read and change your project. Mendix's Marketplace listing for a related extension, MCP for Studio Pro, says the purpose is allowing tools like Claude, Cursor, and GitHub Copilot to read, create, modify, and manage your Mendix application models programmatically. That separate extension says the server runs locally and is accessible only on localhost. That's the design expectation, and the built-in server in the affected versions failed to enforce it.
Siemens' interim mitigation: keep strict inbound firewall policies, such as Windows Defender Firewall, that block external traffic on port 7782. Siemens says this is already the default on standard Windows installations. If you need remote access, use a secure, authenticated channel such as a VPN or SSH tunnel rather than a direct inbound firewall rule.
"Default on standard installations" doesn't mean safe on your installation. Developer workstations often accumulate permissive firewall rules, such as an "allow everything for this app" prompt someone clicked months ago, or exceptions added for local testing. Check the actual configuration rather than assuming the default still applies.
Section summary: The flaw lets other machines on the network reach the server. A blocked port 7782 limits the risk, but the fix is the update.
CVE-2026-112137: CSRF from a malicious web page
The second issue works through the browser. The affected products MCP Server does not properly validate Content-Type and Origin headers on incoming HTTP requests, leaving it vulnerable to Cross-Site Request Forgery (CSRF). This could allow a malicious web page to trick a user's browser into sending unauthorized requests and executing unintended actions on the local MCP Server.
Key details:
- CWE: CWE-352, Cross-Site Request Forgery
- CVSS v3.1: 5.4 (Medium), vector
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L - CVSS v4.0: 5.1
A firewall doesn't help much here, because the request comes from the developer's own browser on the same machine. The attack is an inside job, and a web page you visited is giving the orders. Checking the Origin header is how a local server normally tells a legitimate local tool apart from a random website, and that check was missing.
Siemens' interim mitigation: use modern Chromium- or WebKit-based browsers with Private Network Access protections enabled. Alternatively, use extensions such as uBlock Origin or NoScript to stop external websites from sending fetch requests to localhost (127.0.0.1). The advisory doesn't name browser versions or specific settings, so treat this as general guidance rather than a step-by-step recipe. It reduces risk but doesn't replace the update.
Section summary: This is a lower-scoring bug that a firewall can't stop. Update Studio Pro, and keep browser protections against localhost requests in place in the meantime.
Is anyone exploiting this?
There's no public evidence of exploitation so far. The threat-tracking site OffSeq Radar lists no public exploit code for CVE-2026-112136 and notes it is not in CISA KEV and no source reports exploitation. That's a third-party aggregator, not an official statement, so read it as "nothing seen yet," not "safe forever."
A practical checklist for Windows admins
These steps follow Siemens' guidance. The PowerShell and command-line checks are standard Windows tools, not commands from the Mendix advisory.
- Find your installs. Check developer machines for Studio Pro versions 11.15.x and 11.12.6. Developers often have several versions installed side by side, so check every version, not just the newest.
- Update. Move each install to 11.16.0 or later, or 11.12.7 or later, depending on its line.
- Reconnect MCP clients. Following the Mendix 11.12.7 release note, disconnect and reconnect any connected AI coding client after updating.
- Check the port while you wait. On a machine running Studio Pro,
Get-NetTCPConnection -LocalPort 7782ornetstat -ano | findstr :7782shows whether something is listening and on which address. A listener on0.0.0.0instead of127.0.0.1means it accepts connections from other machines. - Audit firewall rules. Confirm that no inbound rule allows external traffic to port 7782, and remove any old "allow" exceptions for Studio Pro you don't need.
- Tighten browsers. Apply Siemens' browser mitigations, especially on machines where developers browse the web while Studio Pro is running.
Why this matters
These bugs show a recurring problem with AI tooling. Vendors are adding MCP servers to IDEs so assistants can act on a developer's project, and each one is a new local web service with real write access to code. A misconfigured localhost service has caused trouble many times before. The difference now is that the service can also edit your application model.
To keep this in proportion: the affected ranges are small, the fixes shipped quickly (the 11.12.7 build was available before the advisory went public), and Siemens doesn't claim any exploitation. The tags CISA uses (Critical Manufacturing, Energy) reflect where Siemens products are deployed. They don't mean every Studio Pro laptop sits on a factory network.
In short, update Studio Pro and keep port 7782 closed to other machines.
References
- Siemens Mendix Studio Pro CISA · 2026-11-17T12:00:00+00:00
- CVE-2026-112136: Mendix Studio Pro 11 · Binding to an Unrestricted… radar.offseq.com
- Update Security Advisories for SSA-710379 by MarkvanMents · Pull Request #12217 · mendix/docs · GitHub github.com