Is CVE-2026-123544 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-123544 being exploited in the wild.

How severe is CVE-2026-123544?

Medium severity, with a CVSS score of 6.8, published 8 November 2026.

Which products and versions are affected?

Open Identity Platform OpenAM before 16.1.4; Open Identity Platform OpenAM Client SDK before 16.1.4.

How is CVE-2026-123544 attacked?

It is attacked from the adjacent network or over the network, in a hosted service.

Am I affected by CVE-2026-123544?

Check whether you run Open Identity Platform OpenAM or Open Identity Platform OpenAM Client SDK 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.

CVE-2026-123544: OpenAM insufficient validation of internal SOAP responses

CVE-2026-123544 · Severity: medium · CVSS 6.8 · Published 2026-11-08

OpenAM is an identity and access management platform that coordinates authentication and authorization across enterprise systems. A flaw in how it validates responses between internal servers and client applications over SOAP allows attackers positioned on the network to crash services, modify files, or potentially run code without reaching the system from the internet.

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

Quick answers

Is CVE-2026-123544 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-123544 being exploited in the wild.
How severe is CVE-2026-123544?: Medium severity, with a CVSS score of 6.8, published 8 November 2026.
Which products and versions are affected?: Open Identity Platform OpenAM before 16.1.4; Open Identity Platform OpenAM Client SDK before 16.1.4.
Is there a fix for CVE-2026-123544?: Yes: fixed in OpenAM 16.1.4. Until then: Use HTTPS with certificate validation for all communication between OpenAM servers and between SDK clients and OpenAM servers. Ensure server URLs use HTTPS, keep server-to-server traffic on trusted network segments, and restrict administrative and host-level access to limit the blast radius of any server compromise. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-123544 attacked?: It is attacked from the adjacent network or over the network, in a hosted service.
Am I affected by CVE-2026-123544?: Check whether you run Open Identity Platform OpenAM or Open Identity Platform OpenAM Client SDK 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

Use HTTPS with certificate validation for all communication between OpenAM servers and between SDK clients and OpenAM servers. Ensure server URLs use HTTPS, keep server-to-server traffic on trusted network segments, and restrict administrative and host-level access to limit the blast radius of any server compromise.

Technical details

OpenAM and its client SDK fail to sufficiently validate responses on the internal server-to-server SOAP channel (CWE-470, unsafe reflection). An adjacent network attacker who can intercept unencrypted traffic or has compromised a server in a multi-server deployment can tamper with SOAP responses to cause denial of service, file tampering, or possible code execution in the receiving process. The vulnerability requires the attacker to be on the network path or have existing system compromise; external federation partners and single-server deployments without the SDK are not exposed.

Affected products

Open Identity Platform OpenAM before 16.1.4
Open Identity Platform OpenAM Client SDK 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.