---
id: "CVE-2026-123538"
page: "https://infrastack.ai/live/CVE-2026-123538"
kind: "vulnerability"
aliases: ["CVE-2026-123538"]
title: "OpenAM: forged SAML 1.x assertions let a partner sign in as others"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["identity", "openam", "other", "saml", "sso"]
not_affected_if: ["no-saml-1x-partners", "version-16.1.4-or-later"]
published_at: "2026-11-08T02:16:44+00:00"
first_seen_at: "2026-11-08T02:21:10+00:00"
updated_at: "2026-11-08T02:23:24+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123538", "first_seen_at": "2026-11-08T02:21:10+00:00"}]
exploit_sources: []
---

# OpenAM: forged SAML 1.x assertions let a partner sign in as others

Link for people: https://infrastack.ai/live/CVE-2026-123538 (this .md is for agents)

OpenAM before 16.1.4 accepts a signed SAML 1.x assertion if it is signed by any certificate in its keystore, not necessarily the named issuer's. An attacker holding a trusted SAML 1.x partner's private key can forge assertions for another partner and sign in as that partner's users, including privileged ones.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the OpenAM version in use; the sources say versions before `16.1.4` are affected.
- Confirm whether SAML 1.x partner federation is configured on the deployment.

## Fix

- OpenAM: upgrade to `16.1.4` or later (per the sources).

## Timeline

- 2026-11-08T02:21:10+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123538

## Documents

- [advisory] Vendor advisory: github.com https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-j56q-q3r3-hg7f
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/openam-before-16.1.4-saml-1-x-signature-verification-issuer-impersonation

## From the sources

OpenAM before 16.1.4 does not verify that a signed SAML 1.x assertion or response was signed by the partner named as its issuer, accepting a signature from any certificate in OpenAM's keystore. An attacker holding such a private key, such as a trusted SAML 1.x partner, can forge assertions claiming another partner's issuer and sign in as that partner's users, including privileged ones.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_