Problem
The Studio Pro installer downloads and installs third-party components if they are not present on the system: Eclipse Temurin JDK, Git for Windows, .NET Desktop Runtime, Gradle, Visual C++ Redistributable, Native Mobile Builder and Version Selector. The exact versions are not documented anywhere. The only hint is the example file names in the offline installation section of the docs, which are not kept in sync with the installer.
Enterprise customers have to verify every installer package against their vulnerability management policy before rollout. Today this means running the installer on a clean VM to find out which versions it ships. For 11.12.6 LTS this revealed Temurin 21.0.5+11 (October 2024) and Git 2.48.1 (January 2025), both with multiple known high-severity CVEs. Mendix R&D has since confirmed the need to upgrade and announced updated components for 11.12.8 (support ticket 290583), but without published version information customers cannot verify this in future releases either.
Proposal
For every Studio Pro release, publish the exact versions of all bundled or downloaded third-party components, either in the release notes or in a dedicated section of the system requirements. Ideally provide a machine-readable SBOM (CycloneDX or SPDX) for the installer, in the same way Mendix already supports SBOM generation for apps.
Benefit
Customers can assess the security posture of a release before deployment, plan the offline installation with current packages, and track bundled components in their own vulnerability management. For Mendix, this is groundwork for the EU Cyber Resilience Act, whose Annex I requirements (including SBOM and vulnerability handling for components) apply from 11 December 2027.