Is CVE-2026-41573 exploited in the wild?

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

How severe is CVE-2026-41573?

High severity, with a CVSS score of 4, published 15 September 2026.

Which products and versions are affected?

org.openidentityplatform.openam:openam-core-rest (Maven) <= 16.0.6, ECOSYSTEM:introduced=0,fixed=16.1.1; Open Identity Platform OpenAM <= 16.0.6.

Is there a fix for CVE-2026-41573?

Yes. org.openidentityplatform.openam:openam-core-rest (Maven): upgrade to 16.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41573 attacked?

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

Am I affected by CVE-2026-41573?

Check whether you run org.openidentityplatform.openam:openam-core-rest (Maven) or 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.

CVE-2026-41573: Open Identity Platform OpenAM LDAP injection in CREST REST API

Q: Is there a fix for CVE-2026-41573?

Yes. org.openidentityplatform.openam:openam-core-rest (Maven): upgrade to 16.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-41573 attacked?

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

Q: Am I affected by CVE-2026-41573?

Check whether you run org.openidentityplatform.openam:openam-core-rest (Maven) or 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.

CVE-2026-41573 · Severity: high · CVSS 4 · Published 2026-09-15

OpenAM, an open-source identity and access management platform, is vulnerable to a security flaw in its user and group query interfaces. An attacker with a valid session token can send specially crafted requests to extract sensitive information from the underlying user directory. This could lead to the exposure of user lists or other directory data, potentially compromising the privacy of the identity system.

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

Quick answers

Is CVE-2026-41573 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41573 being exploited in the wild.
How severe is CVE-2026-41573?: High severity, with a CVSS score of 4, published 15 September 2026.
Which products and versions are affected?: org.openidentityplatform.openam:openam-core-rest (Maven) <= 16.0.6, ECOSYSTEM:introduced=0,fixed=16.1.1; Open Identity Platform OpenAM <= 16.0.6.
Is there a fix for CVE-2026-41573?: Yes. org.openidentityplatform.openam:openam-core-rest (Maven): upgrade to 16.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41573 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-41573?: Check whether you run org.openidentityplatform.openam:openam-core-rest (Maven) or 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

org.openidentityplatform.openam:openam-core-rest (Maven): upgrade to 16.1.1 or later

# set org.openidentityplatform.openam:openam-core-rest to 16.1.1 in your pom.xml or build.gradle

Technical details

An LDAP injection vulnerability exists in OpenAM's CREST REST API layer, specifically within the `IdentityResourceV1.queryCollection()` method. The `_queryId` HTTP parameter is passed to a `CrestQuery` object with the `escapeQueryId` flag explicitly set to `false`, bypassing previous security fixes (CVE-2021-29156). This unsanitized input reaches `DJLDAPv3Repo.getFilter()`, where it is concatenated into an LDAP filter string. Authenticated attackers with a valid SSO token can exploit this to inject arbitrary LDAP metacharacters via the `/json/{realm}/users` or `/json/{realm}/groups` endpoints. This enables user enumeration and blind LDAP injection against the backend directory. The issue is fixed in version 16.1.1.

Affected products

Open Identity Platform OpenAM <= 16.0.6

Identifiers

CVE-2026-41573
GHSA-2vg8-q4c2-5cw3

Timeline

2026-06-20: disclosed
2026-06-22: advisory: GitHub Advisory published
2026-06-22: patched: Version 16.1.1 released

References

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