A vulnerability has been identified in Mendix Studio Pro 11 (All versions >= V11.15.0 < V11.16.0), Mendix Studio Pro 11.12 (All versions…
Mendix Studio Pro 11 versions from V11.15.0 before V11.16.0 and Studio Pro 11.12 versions from V11.12.6 before V11.12.7 are affected. No vendor rating is given. Fixed in V11.16.0 and V11.12.7.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in V11.16.0, V11.12.7
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Mendix Studio Pro 11 versions >= V11.15.0 < V11.16.0 Mendix Studio Pro 11.12 versions >= V11.12.6 < V11.12.7
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The MCP Server in Mendix Studio Pro 11 is affected, and its HTTP listener is not properly limited to the local loopback interface, so an attacker can reach it remotely over the network without logging in, though a user must take some action for the attack to work. A successful attack could let the attacker interact with the MCP Server, which may put its confidentiality, integrity, and availability at risk.
Read the original description
A vulnerability has been identified in Mendix Studio Pro 11 (All versions >= V11.15.0 < V11.16.0), Mendix Studio Pro 11.12 (All versions >= V11.12.6 < V11.12.7). 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.
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Mendix Studio Pro 11 versions >= V11.15.0 < V11.16.0 Mendix Studio Pro 11.12 versions >= V11.12.6 < V11.12.7Upgrade to a fixed version: V11.16.0, V11.12.7.
Workaround: Maintain strict inbound firewall policies blocking external traffic on port 7782, or restrict remote access through a secure, authenticated channel such as a VPN or SSH tunnel.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-112136 (A vulnerability has been identified in Mendix Studio Pro 11 (All versions >= V11.15.0 < V11.16.0), Mendix Studio Pro 11.12 (All versions…), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-112136 (entry last updated 2026-11-10): Affected: - Siemens Mendix Studio Pro 11: from V11.15.0, fixed in V11.16.0 - Siemens Mendix Studio Pro 11.12: from V11.12.6, fixed in V11.12.7 Fixed versions: V11.16.0, V11.12.7. Conditions (all must be true for the bug to be hit): - Mendix Studio Pro 11 versions >= V11.15.0 < V11.16.0 (source: https://cert-portal.siemens.com/productcert/html/ssa-710379.html) - Mendix Studio Pro 11.12 versions >= V11.12.6 < V11.12.7 (source: https://cert-portal.siemens.com/productcert/html/ssa-710379.html) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, a user action. Workaround: Maintain strict inbound firewall policies blocking external traffic on port 7782, or restrict remote access through a secure, authenticated channel such as a VPN or SSH tunnel. (source: https://cert-portal.siemens.com/productcert/html/ssa-710379.html) CISA KEV: CVE-2026-112136 is not listed as of cve.now's last read. This KEV status is for CVE-2026-112136 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://cert-portal.siemens.com/productcert/html/ssa-710379.html Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-112136 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-112136.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Siemens Mendix Studio Pro 11
From V11.15.0 · fixed in V11.16.0
- Siemens Mendix Studio Pro 11.12
From V11.12.6 · fixed in V11.12.7
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112136
Is CVE-2026-112136 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The Mendix Studio Pro MCP Server's HTTP listener is not restricted to the loopback interface. This means a party with network access could interact with the MCP Server remotely.Source: cert-portal.siemens.com
Which versions are affected by CVE-2026-112136?
Mendix Studio Pro 11: from V11.15.0 before V11.16.0. Mendix Studio Pro 11.12: from V11.12.6 before V11.12.7.Source: cve.now feed data
Am I affected, and how do I check?
Mendix Studio Pro 11 versions from V11.15.0 before V11.16.0 and Mendix Studio Pro 11.12 versions from V11.12.6 before V11.12.7 are listed as affected. Compare the installed Studio Pro version against these ranges.Source: cert-portal.siemens.com
How do I fix CVE-2026-112136?
Update to V11.16.0 or later, or to V11.12.7 or later on the 11.12 line. Until updated, maintain strict inbound firewall policies blocking external traffic on port 7782, or restrict remote access through a secure, authenticated channel such as a VPN or SSH tunnel.Source: cert-portal.siemens.com