dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-48192

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in Mendix Studio Pro 10.11 (All versions), Mendix Studio Pro 10.12 (All versions), Mendix Studio Pro 10.13 (All versions), Mendix Studio Pro 10.14 (All versions), Mendix Studio Pro 10.15 (All versions), Mendix Studio Pro 10.16 (All versions), Mendix Studio Pro 10.17 (All versions), Mendix Studio Pro 10.18 (All versions), Mendix Studio Pro 10.19 (All versions), Mendix Studio Pro 10.20 (All versions), Mendix Studio Pro 10.21 (All versions), Mendix Studio Pro 10.22 (All versions), Mendix Studio Pro 10.23 (All versions), Mendix Studio Pro 10.24 (All versions < V10.24.21), Mendix Studio Pro 11.0 (All versions), Mendix Studio Pro 11.1 (All versions), Mendix Studio Pro 11.10 (All versions), Mendix Studio Pro 11.11 (All versions), Mendix Studio Pro 11.2 (All versions), Mendix Studio Pro 11.3 (All versions), Mendix Studio Pro 11.4 (All versions), Mendix Studio Pro 11.5 (All versions), Mendix Studio Pro 11.6 (All versions < V11.6.7), Mendix Studio Pro 11.7 (All versions), Mendix Studio Pro 11.8 (All versions), Mendix Studio Pro 11.9 (All versions). Affected versions of Mendix Studio Pro do not properly validate or sanitize project files processed during the build pipeline. This could allow an attacker who tricks a user into opening and running a specially crafted malicious project locally on their system to execute arbitrary code in the context of that user.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Mendix Studio Pro fails to properly validate or sanitize project files during the build pipeline, allowing specially crafted malicious .mxd or project files to execute arbitrary code in the context of the user who opens them.

MitigationUpgrade Mendix Studio Pro to version 10.24.21 or later (for v10) or 11.6.7 or later (for v11.6), and only open project files from trusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
High
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Mendix Studio Pro installation
    Check for Mendix Studio Pro in installed programs (Windows: Programs and Features, or look for installation directory typically under C:\Program Files\Mendix).
    Affected if Mendix Studio Pro is not installed on the system.
  2. Identify installed version number
    Open Mendix Studio Pro and navigate to the About dialog (Help > About Mendix Studio Pro) to view the exact version number, or check the installation directory for version information.
    Affected if The version is v10.x before 10.24.21, or v11.6.x before 11.6.7.
  3. Determine if .mxd project files are opened
    Review whether users in the environment commonly open .mxd project files, especially from external or untrusted sources. Check recent file access logs or user workflows.
    Affected if Users open .mxd project files from untrusted or external sources.
  4. Check for build pipeline usage
    Identify if the build pipeline functionality is used (project files are processed through the build pipeline). Review recent build histories or project workflows.
    Affected if The build pipeline processes project files without additional sandboxing.

A user is affected if Mendix Studio Pro v10 before 10.24.21 or v11.6 before 11.6.7 is installed and users open .mxd project files from untrusted sources through the build pipeline.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Mendix Studio Pro to version 10.24.21 or later (for v10) or 11.6.7 or later (for v11.6), and only open project files from trusted sources.

Recommended fix Moderate confidence

Upgrade to Mendix Studio Pro 10.24.21 or later (for 10.x versions) OR upgrade to 11.6.7 or later (for 11.x versions)

  1. 1. Identify the currently installed Mendix Studio Pro version by opening the application and checking 'Help > About Mendix Studio Pro'
  2. 2. For Mendix Studio Pro 10.x users: Upgrade to version 10.24.21 or later from the official Mendix download portal
  3. 3. For Mendix Studio Pro 11.x users (11.0-11.5): Upgrade to version 11.6.7 or later from the official Mendix download portal
  4. 4. For Mendix Studio Pro 11.x users (11.6): Upgrade to version 11.6.7 or later from the official Mendix download portal
  5. 5. For Mendix Studio Pro 11.x users (11.7-11.11): Contact Mendix support to confirm if a patch is available or upgrade to the latest stable release
  6. 6. After upgrading, verify the installation by checking 'Help > About Mendix Studio Pro' shows the patched version
  7. 7. Exercise caution when opening Mendix project files (.mpr) from untrusted sources, as the vulnerability exploits the build pipeline processing
Caveat Review Mendix release notes for breaking changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48192 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data