# CVE-2026-123550: OpenAM SAML v2.0 service provider authentication bypass

Source: https://junglewise.ai/threats/cve-2026-123550-openam-before-16-1-4-contains-an-authentication-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-08. Updated: 2026-11-08  
License: CC BY 4.0 with a link back

CVE-2026-123550 · Severity: critical · CVSS 9.8 · Published 2026-11-08

OpenAM is an identity and access management platform that handles user authentication and single sign-on for enterprise applications. The vulnerability allows unauthenticated attackers to forge SAML authentication assertions and gain sessions as any user, including administrators, without requiring valid credentials. An attacker exploiting this could take over user accounts and hijack access to all dependent applications relying on that OpenAM instance for authentication.

Technologies: [Open Identity Platform OpenAM](https://junglewise.ai/threats/technologies/openam). Vendors: [Open Identity Platform](https://junglewise.ai/threats/vendors/open-identity-platform).

## Quick answers

**Is CVE-2026-123550 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-123550 being exploited in the wild.

**How severe is CVE-2026-123550?** Critical severity, with a CVSS score of 9.8, published 8 November 2026.

**Which products and versions are affected?** Open Identity Platform OpenAM before 16.1.4.

**Is there a fix for CVE-2026-123550?** Yes: fixed in OpenAM 16.1.4. Until then: Enable Assertions Signed (WantAssertionsSigned=true) for all hosted service providers in Federation > Entity Providers before upgrading, after confirming all trusted identity providers sign their assertions. Remove the ECP (PAOS) assertion consumer service from hosted service provider metadata if ECP is not used, and block requests to the ECP endpoint at the reverse proxy. Do not configure encryption keys on service providers that do not require encrypted assertions, and ensure all artifact resolution services use HTTPS.</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-123550 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-123550?** 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 OpenAM 16.1.4

Enable Assertions Signed (WantAssertionsSigned=true) for all hosted service providers in Federation > Entity Providers before upgrading, after confirming all trusted identity providers sign their assertions. Remove the ECP (PAOS) assertion consumer service from hosted service provider metadata if ECP is not used, and block requests to the ECP endpoint at the reverse proxy. Do not configure encryption keys on service providers that do not require encrypted assertions, and ensure all artifact resolution services use HTTPS.</anigation>
<parameter name="timeline">[{"kind":"disclosed","at":"2026-10-22"},{"kind":"advisory","at":"2026-11-08"}]

## Technical details

OpenAM's SAML v2.0 service provider fails to enforce signature validation on assertions received via ECP (PAOS) and HTTP-Artifact bindings when the WantAssertionsSigned configuration is set to false (the default). An unauthenticated remote attacker can submit unsigned or forged assertions to obtain valid sessions, with no user interaction required. The vulnerability is only exploitable when the service provider has an encryption key configured and meets specific binding conditions; upgrading to 16.1.4 enforces mandatory signature validation on all bindings regardless of configuration.

## Affected products

- Open Identity Platform OpenAM before 16.1.4

## References

- [https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-3j2f-qhrc-rjfj](https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-3j2f-qhrc-rjfj)
- [https://www.vulncheck.com/advisories/openam-before-16.1.4-saml-authentication-bypass-via-unsigned-assertions](https://www.vulncheck.com/advisories/openam-before-16.1.4-saml-authentication-bypass-via-unsigned-assertions)

## Related threats

- [OpenAM default credentials authentication bypass in built-in identities](https://junglewise.ai/threats/cve-2026-123553-openam-before-16-1-4-ships-built-in-identities-in-the-top-level)
- [OpenAM unauthenticated session token disclosure via WebSocket](https://junglewise.ai/threats/cve-2026-123551-openam-from-14-0-0-before-16-1-4-contains-an-information)
- [OpenAM self-registration attribute list enforcement bypass](https://junglewise.ai/threats/cve-2026-123549-openam-before-16-1-4-fails-to-enforce-the-valid-creation)
- [OpenAM open redirect via SAML RelayState](https://junglewise.ai/threats/cve-2026-123547-openam-before-16-1-4-contains-an-open-redirect-vulnerability)
- [OpenAM open redirect and cross-site scripting in goto parameter](https://junglewise.ai/threats/cve-2026-123546-openam-before-16-1-4-contains-an-open-redirect-and-cross-site)