Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-80465 – Authentication Bypass / Account Hijacking – Mendix SAML Module (Mendix 9.24, 10, 11

Be the first to know when new zero-days emerge:

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/)

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge