On November 8, 2026, NVD published three OpenAM CVEs scored 9.8 to 10.0 by VulnCheck. OpenAM is an access management and single sign-on server: it authenticates users and issues the sessions that other applications then trust without a second look.
That's what makes these serious. Each one, by a different route, hands out an administrator session — or any user's — with no prior authentication. And an OpenAM session also opens every application that trusts it.
All three are fixed in the same release: OpenAM 16.1.4, according to the descriptions.
The Three Vulnerabilities
| CVE | Nature (CWE) | CVSS 3.1 (VulnCheck) | CVSS 4.0 (VulnCheck) | Versions (NVD description) |
|---|---|---|---|---|
| CVE-2026-123551 | Session tokens exposed on the notification WebSocket (CWE-201) | 10.0 — AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | 10.0 | 14.0.0 up to before 16.1.4 |
| CVE-2026-123550 | Unsigned SAML assertions accepted (CWE-290) | 9.8 — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | 9.3 | before 16.1.4 |
| CVE-2026-123549 | Restricted attributes settable at self-registration (CWE-269) | 9.8 — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | 9.3 | before 16.1.4 |
- NVD publication: 2026-11-08
- NVD status: Received — no NVD score, no CPE configuration. Scores come from VulnCheck, the CNA for these CVEs.
- Advisories: GitHub OpenIdentityPlatform/OpenAM (GHSA-5c3q-hp86-xjr8, GHSA-3j2f-qhrc-rjfj, GHSA-jv8f-m88g-h6mm) and VulnCheck advisories
- CISA KEV: no
CVE-2026-123551: Session Tokens Anyone Can Read
NVD description:
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.
OpenAM pushes notifications to its agents — the components guarding each application — over a WebSocket that's meant for agents only. Per the description, that agent-only check can be bypassed through an unvalidated internal forward on the legacy Liberty ID-FF endpoints. An unauthenticated attacker can then read live iPlanetDirectoryPro tokens — OpenAM's session cookies — and hijack user and administrator sessions.
The 10.0 comes from S:C: a stolen token is just as good on every application OpenAM protects.
CVE-2026-123550: Forged SAML Assertions Accepted
Acting as a SAML v2.0 service provider, OpenAM accepts unsigned assertions on the ECP (PAOS) and HTTP-Artifact bindings when WantAssertionsSigned is false. An unauthenticated attacker can submit a forged assertion and get a session as any mapped user, administrators included, then ride single sign-on into dependent applications.
Worth noting: WantAssertionsSigned = false doesn't mean "nothing is signed". You'll find that setting in deployments where the SAML response is signed rather than the assertion. The issue described lies in those two bindings, which then accept an assertion with no signature at all — so a configuration that looks careful can still be exposed.
CVE-2026-123549: Registering Straight Into an Admin Group
OpenAM doesn't enforce its Valid Creation Attributes list during self-registration. An anonymous user can set restricted attributes — group membership among them — through the legacy self-service REST endpoint or the User Self-Service flow, and join an administrative group. The stated result: full administrative control of OpenAM.
This one requires self-registration to be reachable. If you've disabled it, that's the first thing to confirm, not a free pass: the other two CVEs don't depend on that feature.
Affected Versions
| CVE | First affected version | First version outside the range |
|---|---|---|
| CVE-2026-123551 | 14.0.0 | 16.1.4 |
| CVE-2026-123550 | not specified ("before 16.1.4") | 16.1.4 |
| CVE-2026-123549 | not specified ("before 16.1.4") | 16.1.4 |
⚠️ These bounds come from the NVD descriptions — NVD hasn't published a CPE configuration yet. 16.1.4 is the first version outside the range, not necessarily the latest release: check the project's GitHub advisories for the recommended version.
Detection
- Requests to the legacy Liberty ID-FF endpoints and notification WebSocket connections from addresses that aren't your agents (CVE-2026-123551)
- Sessions used from two different addresses in a short window — a sign of a replayed token
- SAML logins over ECP (PAOS) or HTTP-Artifact with no matching transaction on the IdP side (CVE-2026-123550)
- Self-registered accounts that belong to an administrative group (CVE-2026-123549): check the full history, not just since disclosure
Mitigation
1. Upgrade to 16.1.4 or later
It's the only fix for all three CVEs.
2. In the meantime
- Block the Liberty ID-FF endpoints at the reverse proxy if you don't use them, and restrict the notification WebSocket to your agents' addresses
- Disable self-registration and the legacy self-service REST endpoint if they're not needed
- Require signed assertions (
WantAssertionsSigned) on the service provider side, and disable the ECP and HTTP-Artifact bindings if you don't rely on them
3. After upgrading
- Invalidate every active session: a token that's already been stolen stays valid until it expires
- Rotate administrator passwords
- Review administrative group membership and remove self-registered accounts that don't belong there
Why Continuous Monitoring of Your Identity Stack Matters
An SSO server is a single point of trust: compromise it and you compromise everything that relies on it. And a component like OpenAM — often installed years ago, then forgotten behind the applications it protects — is rarely in the first inventory anyone checks when a CVE drops.
With cveo.tech, add your identity servers to your inventory with their exact version and get alerted as soon as a CVE affects them, even before NVD has analyzed it.