CVE-2026-123551: OpenAM unauthenticated session token disclosure via WebSocket

CVE-2026-123551 · Severity: critical · CVSS 10 · Published 2026-11-08

OpenAM is an identity and access management platform that manages user authentication and sessions for enterprise applications. An unauthenticated attacker on the network can bypass authentication checks and passively collect live session tokens from the notification WebSocket, enabling them to hijack any user's account including administrators. This could lead to complete administrative compromise, data theft, and lateral movement to dependent applications, all without triggering authentication failures or logs of unauthorized access attempts.

Technologies: Open Identity Platform OpenAM. Vendors: Open Identity Platform.

Quick answers

Is CVE-2026-123551 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-123551 being exploited in the wild.
How severe is CVE-2026-123551?
Critical severity, with a CVSS score of 10, published 8 November 2026.
Which products and versions are affected?
Open Identity Platform OpenAM 14.0.0 to 16.1.3.
Is there a fix for CVE-2026-123551?
Yes: fixed in 16.1.4. Until then: Restrict network access to /openam/notifications and /openam/ws/* at the reverse proxy or firewall to only legitimate agent hosts. Alternatively, disable agent notifications by setting the property org.forgerock.openam.notifications.agents.enabled to false if agents do not depend on them, or block the legacy Liberty ID-FF endpoints entirely.</anigation> <parameter name="timeline">[ { "kind": "disclosed", "at": "2026-10-22" }, { "kind": "advisory", "at": "2026-11-08" } ] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-123551 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-123551?
Check whether you run Open Identity Platform OpenAM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 16.1.4

Restrict network access to /openam/notifications and /openam/ws/* at the reverse proxy or firewall to only legitimate agent hosts. Alternatively, disable agent notifications by setting the property org.forgerock.openam.notifications.agents.enabled to false if agents do not depend on them, or block the legacy Liberty ID-FF endpoints entirely.</anigation> <parameter name="timeline">[ { "kind": "disclosed", "at": "2026-10-22" }, { "kind": "advisory", "at": "2026-11-08" } ]

Technical details

OpenAM broadcasts full session identifiers (iPlanetDirectoryPro tokens) to a notification WebSocket intended only for policy agents, but the agent-only authentication check can be bypassed via an unvalidated internal request forward on legacy Liberty ID-FF endpoints. An unauthenticated attacker on the network can connect to the WebSocket and subscribe to internal topics to passively collect active session tokens, which are usable directly as bearer credentials. The vulnerability is fixed in OpenAM 16.1.4 by restricting the notification topics to agent-only subscriptions, securing the Liberty ID-FF endpoints, and applying security filters to internal request dispatches.

Affected products

  • Open Identity Platform OpenAM 14.0.0 to 16.1.3

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.