Siemens Mendix System.User Access Docs Flaw
A Siemens Mendix Runtime documentation gap can lead developers to misconfigure access rules on System.User, exposing sensitive data or enabling privilege escalation.
Sourcecisa.gov — open the original
What to check
- Applies to
- The 1 CVE named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
Siemens has disclosed a documentation deficiency in Mendix Runtime concerning the System.User entity's special access-control behavior. Because the official documentation does not clearly explain that System.User has built-in, platform-enforced permissions that cannot be overridden by developer-defined access rules on specializations, application developers may unknowingly configure overly permissive rules. A common real-world misconfiguration involves granting the anonymous user role access via a System.User specialization, inadvertently exposing all stored user records even when no explicit access rights were configured for that role.
This issue, tracked as CVE-2026-7891 and classified under CWE-277 (Insecure Inherited Permissions), affects all versions of Siemens Mendix Runtime. Siemens recommends that developers revise any security model relying on XPath constraints applied to System.User specializations, instead enforcing restrictions at the App Security role-management configuration level, and consult updated Mendix documentation for guidance. There is no evidence of active exploitation; this is a proactive vendor disclosure aimed at preventing insecure application configurations across the worldwide Mendix deployment base, primarily impacting the critical manufacturing sector per CISA's advisory categorization.
No indicators of compromise, threat actors, or malware are associated with this advisory. The risk stems from developer misconfiguration enabled by inadequate documentation rather than a code-level vulnerability, making remediation a matter of application-level review and reconfiguration rather than patching.
Mentioned in this report
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-26-209-02
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,433 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs