Skip to content
major vulnerability· requires attention

OpenAM is a widely used enterprise IAM platform; unauthenticated auth bypass enables session takeover across organizations.

Applications

CVE-2026-46619

9.3
Critical
EPSS 0.58%Patch availableSep 15, 2026

Unauthenticated LDAP injection in OpenAM allows attacker session takeover

common questions

Is CVE-2026-46619 being exploited?

Not confirmed. CVE-2026-46619 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.58% probability of exploitation in the next 30 days.

How severe is CVE-2026-46619?

CVE-2026-46619 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-46619?

Yes. A fix has been recorded for CVE-2026-46619. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-46619 affect?

CVE-2026-46619 affects OpenAM (Open Identity Platform) MSISDN auth module, OpenAM versions prior to 16.1.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46619?

Upgrade to OpenAM 16.1.1 immediately; disable MSISDN auth or restrict access until patched.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OpenAM (Open Identity Platform) MSISDN auth moduleOpenAM versions prior to 16.1.1
impact

Unauthenticated LDAP-filter injection in MSISDN module lets attacker obtain a valid OpenAM session as an arbitrary user.

action required

Immediate action required

affected versions
OpenIdentityPlatform OpenAM
  • affected< 16.1.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free