CVE-2026-123536: OpenAM server-side request forgery in federation configuration wizard

CVE-2026-123536 · Severity: medium · CVSS 4.1 · Published 2026-11-08

OpenAM is an identity and access management platform used to manage user authentication and authorization. Before version 16.1.4, administrators can exploit a flaw in the federation configuration wizard to make the OpenAM server fetch arbitrary URLs, including internal network addresses and cloud metadata endpoints. An attacker with admin privileges can probe internal systems and read partial response data, potentially exposing sensitive configuration or credentials.

Technologies: Open Identity Platform OpenAM. Vendors: Open Identity Platform.

Quick answers

Is CVE-2026-123536 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-123536 being exploited in the wild.
How severe is CVE-2026-123536?
Medium severity, with a CVSS score of 4.1, 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-123536?
Yes: fixed in 16.1.4. Until then: Restrict administrative access to federation configuration to trusted administrators with network-level trust. Block outbound traffic from OpenAM servers to internal hosts and cloud metadata endpoints. Prefer pasting metadata documents directly into wizards instead of providing URLs. Set the advanced property org.openidentityplatform.federation.workflow.allow-any-address to true only for federation partners publishing metadata on internal addresses. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-123536 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-123536?
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: 16.1.4

Restrict administrative access to federation configuration to trusted administrators with network-level trust. Block outbound traffic from OpenAM servers to internal hosts and cloud metadata endpoints. Prefer pasting metadata documents directly into wizards instead of providing URLs. Set the advanced property org.openidentityplatform.federation.workflow.allow-any-address to true only for federation partners publishing metadata on internal addresses.

Technical details

A server-side request forgery (SSRF) vulnerability exists in OpenAM's federation configuration wizards (SAML v2.0 entity import, identity/service provider configuration, circle of trust lookup, and OpenID Connect discovery). The wizards fetch metadata from administrator-supplied URLs without validating the destination, allowing authenticated administrators to request internal or private network addresses. The fix in 16.1.4 restricts URL schemes to HTTP(S), blocks redirects to special-purpose addresses, limits redirects to three hops, and rejects HTTPS-to-HTTP downgrades.

Affected products

  • Open Identity Platform OpenAM before 16.1.4

Timeline

  • 2026-10-22: disclosed
  • 2026-11-08: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.