CVE-2026-123538Medium· 6.6▾ SunlitOpenAM 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, suc…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 36.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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.
OpenAM < 16.1.4Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-105118Medium· 4.7OpenAM before 16.1.3 contains an open redirect vulnerability that allows unauthenticated attackers to redirect users by supplying an unverified id_token_hint to the /oauth2/connect/endSession endpoint
CVE-2026-46560High· 7.5OpenAM Authentication Bypass via RADIUS Spoofing
CVE-2026-123537Medium· 5.0OpenAM before 16.1.4 SSRF via UMA Scope Description URLs
CVE-2026-123536Medium· 4.1OpenAM before 16.1.4 SSRF via Federation Configuration Wizard Metadata URLs
CVE-2026-123539Medium· 4.8OpenAM before 16.1.4 Stored XSS via OAuth 2.0 Consent Page Display Name
CVE-2026-123541Medium· 4.7OpenAM before 16.1.4 Open Redirect via SAML 1.x Trusted-Partner Matching