Summary
CVE-2026-80465 is a high-severity (CVSS 8.7) improper cryptographic signature verification flaw (CWE-347) in the Mendix SAML module. Affected versions fail to properly validate the signature on SAML responses, allowing an unauthenticated remote attacker to hijack a legitimate user’s session in specific SSO configurations. The issue affects the Mendix SAML module compatible with Mendix 9.24, 10, and 11.
Technical details
- Root cause: The Mendix SAML module does not properly verify that the XML digital signature on an incoming SAML response corresponds to the trusted certificate/key of the configured identity provider.
- Trigger conditions: Applies to specific SSO configurations where SAML-based authentication is enabled; an attacker able to submit or modify a SAML assertion to the application’s SSO endpoint can exploit the flaw.
- Attack vector: Network-based; no privileges required; no user interaction; attack complexity is rated high.
- Impact: Successful exploitation lets an unauthenticated remote attacker assume ("hijack") an authenticated user’s session, resulting in high confidentiality and integrity impact within the affected application (scope changed).
Affected software
- Mendix SAML (Mendix 9.24 compatible) — all versions before V3.6.27
- Mendix SAML (Mendix 10 compatible) — all versions before V4.2.3
- Mendix SAML (Mendix 11 compatible) — all versions before V4.2.3
Severity
- CVSS v3.1 Base Score: 8.7 (High)
- Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
Mitigation and recommended actions
- Immediate: Update the Mendix SAML module to the patched release via the Mendix Marketplace:
- Mendix 9.24 compatible → V3.6.27 or later
- Mendix 10 / 11 compatible → V4.2.3 or later
- If immediate patching is not possible: Restrict network access to SSO/SAML endpoints to trusted networks, review and tighten SSO/IdP trust configurations, and monitor authentication logs for anomalous session establishment consistent with SAML response tampering.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
originURI=/SSO/appearing in a query parameter (e.g.,?originURI=/SSO/or&originURI=/SSO/)

