Home › Vulnerabilities

Open Identity Platform OpenAM notification WebSocket Flaw CVE-2026-123551: Update Now

Published November 8, 2026 · Last updated November 8, 2026

CVE Critical Patch

The short version: CVE-2026-123551 is a critical-severity security flaw in Open Identity Platform OpenAM notification WebSocket. The National Vulnerability Database (NVD) published it on November 8, 2026, and the score it lists is 10.0 out of 10. When FraudMeNot checked on November 8, 2026, CISA had not added CVE-2026-123551 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-123551

The record was filed by vulncheck.com. In its own words: "OpenAM from 14.0.0 before 16.1.4 contains an information disclosure vulnerability that allows unauthenticated attackers to read live session tokens from the notification WebSocket. Attackers can bypass the agent-only check through an unvalidated internal forward on legacy Liberty ID-FF endpoints, collecting iPlanetDirectoryPro tokens to hijack user and administrator sessions."

Why OpenAM notification WebSocket admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on vulncheck.com rated CVE-2026-123551 10.0 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping OpenAM notification WebSocket running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.

Scores can differ between the vendor and NVD because each judges the worst realistic case differently. For this flaw, the address listed on vulncheck.com gives it 10.0 (Critical, CVSS 4.0).

Affected OpenAM notification WebSocket releases

According to the record, these releases are vulnerable:

  • 14.0.0 up to, but not including, 16.1.4
  • 14.0.0 up to, but not including, 16.1.4
  • 14.0.0 up to, but not including, 16.1.4

Vendor remediation for CVE-2026-123551

The vendor advisory remediation for operators of OpenAM notification WebSocket, quoted for this page, is: "Patch: OpenAM platform owners should upgrade affected 14.0.0–16.1.3 installations to 16.1.4, including customized dispatcher mappings and legitimate Relay State destinations. Workaround: network administrators should restrict notification access to trusted agent hosts; identity owners should disable unneeded agent notifications and unused ID-FF paths while accounting for cache behavior. Who acts: platform operations own the release, federation teams validate redirects, security operations coordinate session rotation and monitoring, and application owners verify normal agent-dependent access decisions. An attacker needs network reachability to the OpenAM port and the ability to hold a connection to the notification WebSocket. A user must create, change or end a session while that connection is open for the corresponding token to be observed. The most severe administrative outcome additionally depends on activity involving an administrator's session. Those are meaningful prerequisites even though session activity is routine in a working identity deployment. Agent notifications are enabled by default, according to the maintainers. No federation, self-service or agent feature needs separate configuration for the weaknesses to exist in the described default reachable deployment. That distinguishes this issue from registration-only or specially configured SAML flaws. Nevertheless, a private deployment with tightly restricted network paths has a different practical exposure from an internet-reachable instance, and an advisory is not evidence that a particular firewall permits the necessary connection. The vendor states that a captured user token enables impersonation until the session ends. An administrator token carries broader configuration powers and can lead to command execution under the OpenAM service account. This is a conditional consequence described by the source, not proof of host compromise. Passive collection may not produce failed login attempts or account lockouts, so an absence of those signals cannot, by itself, rule out notification exposure. OpenIdentityPlatform rates its advisory Critical with CVSS 3.1 score 10.0. The assigned CVE record hosted by NVD separately contains VulnCheck CNA scores of 10.0 under both CVSS 3.1 and CVSS 4.0. These matching numbers still need separate attribution. The material reviewed does not provide an independent NVD analyst assessment, and the CNA's score should not be described as NVD's own calculation or as an additional vendor CVSS 4.0 rating."

What to do about it

  • Update now: Patch: OpenAM platform owners should upgrade affected 14.0.0–16.1.3 installations to 16.1.4, including customized dispatcher mappings and legitimate Relay State destinations. Workaround: network administrators should restrict notification access to trusted agent hosts; identity owners should disable unneeded agent notifications and unused ID-FF paths while accounting for cache behavior. Who acts: platform operations own the release, federation teams validate redirects, security operations coordinate session rotation and monitoring, and application owners verify normal agent-dependent access decisions. An attacker needs network reachability to the OpenAM port and the ability to hold a connection to the notification WebSocket. A user must create, change or end a session while that connection is open for the corresponding token to be observed. The most severe administrative outcome additionally depends on activity involving an administrator's session. Those are meaningful prerequisites even though session activity is routine in a working identity deployment. Agent notifications are enabled by default, according to the maintainers. No federation, self-service or agent feature needs separate configuration for the weaknesses to exist in the described default reachable deployment. That distinguishes this issue from registration-only or specially configured SAML flaws. Nevertheless, a private deployment with tightly restricted network paths has a different practical exposure from an internet-reachable instance, and an advisory is not evidence that a particular firewall permits the necessary connection. The vendor states that a captured user token enables impersonation until the session ends. An administrator token carries broader configuration powers and can lead to command execution under the OpenAM service account. This is a conditional consequence described by the source, not proof of host compromise. Passive collection may not produce failed login attempts or account lockouts, so an absence of those signals cannot, by itself, rule out notification exposure. OpenIdentityPlatform rates its advisory Critical with CVSS 3.1 score 10.0. The assigned CVE record hosted by NVD separately contains VulnCheck CNA scores of 10.0 under both CVSS 3.1 and CVSS 4.0. These matching numbers still need separate attribution. The material reviewed does not provide an independent NVD analyst assessment, and the CNA's score should not be described as NVD's own calculation or as an additional vendor CVSS 4.0 rating.
  • Who should act: IT teams, managed service providers, and developers who run or ship OpenAM notification WebSocket. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Open Identity Platform (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 8, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-123551. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-123551 record details from CISA and NVD

  • Attack complexity for CVE-2026-123551: low
  • CVE-2026-123551 CVSS scope: changed
  • NVD sub-scores for CVE-2026-123551: exploitability 3.9, impact 6.0.
  • Who mapped the weakness type: the address listed on vulncheck.com (Primary)
  • References in the NVD record: 2.

Dates to know

  • November 8, 2026: NVD publishes CVE-2026-123551.
  • November 8, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-123551 is not listed.
  • November 8, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.