Open Identity Platform OpenAM SAML service provider Flaw CVE-2026-123550: Update Now
Published November 8, 2026 · Last updated November 8, 2026
The short version: CVE-2026-123550 is a critical-severity security flaw in Open Identity Platform OpenAM SAML service provider. The National Vulnerability Database (NVD) published it on November 8, 2026, and the score it lists is 9.8 out of 10. When FraudMeNot checked on November 8, 2026, CISA had not added CVE-2026-123550 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-123550
The record was filed by vulncheck.com. In its own words: "OpenAM before 16.1.4 contains an authentication bypass vulnerability in its SAML v2.0 service provider that accepts unsigned assertions on the ECP (PAOS) and HTTP-Artifact bindings when WantAssertionsSigned is false. Unauthenticated remote attackers can submit forged assertions to obtain sessions as any mapped user, including administrators, and hijack single sign-on to dependent applications."
Why OpenAM SAML service provider admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on vulncheck.com rated CVE-2026-123550 9.8 (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 SAML service provider running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 9.3 (Critical, CVSS 4.0).
Affected OpenAM SAML service provider releases
According to the record, these releases are vulnerable:
- versions before 16.1.4
- versions before 16.1.4
The type of bug behind CVE-2026-123550
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-290, Authentication Bypass by Spoofing. MITRE describes this class of bug as follows: "This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks."
Vendor remediation for CVE-2026-123550
The vendor advisory remediation for operators of OpenAM SAML service provider, quoted for this page, is: "Patch: OpenAM platform administrators should upgrade affected service providers to 16.1.4 and coordinate signing metadata with every identity-provider partner before rollout. Workaround: federation administrators should require signed assertions, remove unused ECP bindings, eliminate unnecessary encryption-key configuration and use HTTPS artifact resolution as the vendor directs; reverse-proxy owners should block unused ECP consumers. Who acts: identity operations own the version and metadata change, partner administrators validate signatures, application teams check normal sign-on, and security operations review privileged ECP activity. OpenAM must act as a hosted SAML v2.0 service provider for the principal issue described by the maintainers. Deployments that do not perform that role are not affected by this SAML issue. For the ECP path, three conditions must hold together: metadata advertises the ECP or PAOS assertion consumer service; Assertions Signed, represented by WantAssertionsSigned, is disabled; and the service provider has an encryption key configured so identity providers can encrypt assertions to it. The generated metadata advertises ECP and leaves the signed-assertion requirement off by default. The encryption key, however, is an administrator-chosen configuration rather than a default. Describing all three conditions as defaults would materially exaggerate exposure. An inventory should therefore distinguish enabled federation roles, advertised bindings, signing requirements and encryption settings rather than treating the presence of OpenAM as a complete assessment. An unauthenticated remote attacker can obtain a session without credentials or user interaction when the vulnerable configuration permits it. Which accounts are reachable depends on assertion-to-account mapping. Attribute-based auto-federation or use of the name identifier as a user identifier can make any account reachable. Otherwise, the attacker needs a federation identifier that is known or guessable, such as an email address or username used as a persistent identifier. Administrative accounts are not excluded, and applications relying on the resulting single-sign-on session can inherit its consequences. The OpenIdentityPlatform advisory assigns CVSS 3.1 score 9.8, Critical. The associated NVD-hosted CVE record separately contains VulnCheck CNA metrics: CVSS 3.1 score 9.8 and CVSS 4.0 score 9.3, also Critical. Those values belong to their named sources and scoring versions. The retrieved record does not supply an independent NVD analyst score; saying that NVD itself rated the issue 9.8 would misattribute the CNA assessment."
What to do about it
- Update now: Patch: OpenAM platform administrators should upgrade affected service providers to 16.1.4 and coordinate signing metadata with every identity-provider partner before rollout. Workaround: federation administrators should require signed assertions, remove unused ECP bindings, eliminate unnecessary encryption-key configuration and use HTTPS artifact resolution as the vendor directs; reverse-proxy owners should block unused ECP consumers. Who acts: identity operations own the version and metadata change, partner administrators validate signatures, application teams check normal sign-on, and security operations review privileged ECP activity. OpenAM must act as a hosted SAML v2.0 service provider for the principal issue described by the maintainers. Deployments that do not perform that role are not affected by this SAML issue. For the ECP path, three conditions must hold together: metadata advertises the ECP or PAOS assertion consumer service; Assertions Signed, represented by WantAssertionsSigned, is disabled; and the service provider has an encryption key configured so identity providers can encrypt assertions to it. The generated metadata advertises ECP and leaves the signed-assertion requirement off by default. The encryption key, however, is an administrator-chosen configuration rather than a default. Describing all three conditions as defaults would materially exaggerate exposure. An inventory should therefore distinguish enabled federation roles, advertised bindings, signing requirements and encryption settings rather than treating the presence of OpenAM as a complete assessment. An unauthenticated remote attacker can obtain a session without credentials or user interaction when the vulnerable configuration permits it. Which accounts are reachable depends on assertion-to-account mapping. Attribute-based auto-federation or use of the name identifier as a user identifier can make any account reachable. Otherwise, the attacker needs a federation identifier that is known or guessable, such as an email address or username used as a persistent identifier. Administrative accounts are not excluded, and applications relying on the resulting single-sign-on session can inherit its consequences. The OpenIdentityPlatform advisory assigns CVSS 3.1 score 9.8, Critical. The associated NVD-hosted CVE record separately contains VulnCheck CNA metrics: CVSS 3.1 score 9.8 and CVSS 4.0 score 9.3, also Critical. Those values belong to their named sources and scoring versions. The retrieved record does not supply an independent NVD analyst score; saying that NVD itself rated the issue 9.8 would misattribute the CNA assessment.
- Who should act: IT teams, managed service providers, and developers who run or ship OpenAM SAML service provider. 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-123550. 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-123550 record details from CISA and NVD
- Attack complexity for CVE-2026-123550: low
- CVE-2026-123550 CVSS scope: unchanged
- NVD sub-scores for CVE-2026-123550: exploitability 3.9, impact 5.9.
- 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-123550.
- November 8, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-123550 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):
- github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-3j2f-qhrc-rjfj
- www.vulncheck.com/advisories/openam-before-16.1.4-saml-authentication-bypass-via-unsigned-
Sources
- NVD: CVE-2026-123550
- CVE.org: CVE-2026-123550
- Open Identity Platform advisory
- Open Identity Platform advisory
- MITRE CWE-290
General education only, not security advice. Facts checked against the sources above on the date shown.