CISA Details Mendix Studio Pro MCP Exposure and Browser Request Flaws
Quick Answer
Update the affected Mendix Studio Pro line and verify MCP listener reachability, port 7782 firewall policy and browser-to-localhost request controls.
Confirm Scope And Apply The Supported Remediation
What to do now: Identify developer workstations, Studio Pro build numbers, enabled MCP servers, listening interfaces and inbound rules for port 7782. Determine whether remote systems can reach the MCP service and whether a developer browser can send requests to it. A default Windows firewall rule is not proof of the workstation’s current policy. Install 11.16.0 or the 11.12.7 maintenance fix. Preserve strict inbound rules on port 7782; use an authenticated VPN or SSH tunnel when remote access is needed. Apply Siemens-recommended browser protections against external websites reaching localhost. Check the listening address and test denied remote connections and rejected cross-origin requests. Confirm approved MCP workflows still work and retain build, policy and regression evidence.
Last verified: 2026-11-17 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Mendix Studio Pro 11 and 11.12 MCP Server |
|---|---|
| Advisory | ICSA-26-321-05 |
| CVEs | CVE-2026-112136, CVE-2026-112137 |
| Authoritative release date | 2026-11-17T12:00:00Z — CISA release timestamp in the advisory page. |
| Authority revision date | No separate material revision is confirmed for this CISA release. |
| Affected versions | Mendix Studio Pro 11 from 11.15.0 before 11.16.0; the 11.12 line from 11.12.6 before 11.12.7. |
| Fixed version | Mendix Studio Pro 11.16.0 or later, or 11.12.7 or later on the 11.12 line |
| CVSS base score | 8.8 (CVSS v3.1, CVE-2026-112136); 5.4 (CVE-2026-112137) |
| CVSS severity | High |
| Exploitation status | The cited CISA ICS advisory does not confirm exploitation of these products in the wild.; no exploitation claim is inferred. |
What Changed
CISA describes an MCP HTTP listener exposed beyond loopback and insufficient Content-Type and Origin validation that permits browser-mediated requests to the local server.
What To Validate Now
- Inventory. Identify developer workstations, Studio Pro build numbers, enabled MCP servers, listening interfaces and inbound rules for port 7782.
- Establish applicability. Determine whether remote systems can reach the MCP service and whether a developer browser can send requests to it. A default Windows firewall rule is not proof of the workstation’s current policy.
- Remediate. Install 11.16.0 or the 11.12.7 maintenance fix. Preserve strict inbound rules on port 7782; use an authenticated VPN or SSH tunnel when remote access is needed. Apply Siemens-recommended browser protections against external websites reaching localhost.
- Validate. Check the listening address and test denied remote connections and rejected cross-origin requests. Confirm approved MCP workflows still work and retain build, policy and regression evidence.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
A firewall addresses remote reachability but does not fully address requests sent by a local browser. The two CVEs need separate validation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

