How severe is GHSA-2vg8-q4c2-5cw3?

No CVSS score has been assigned to GHSA-2vg8-q4c2-5cw3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2vg8-q4c2-5cw3?

GHSA-2vg8-q4c2-5cw3 affects the following packages: org.openidentityplatform.openam:openam-core-rest (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2vg8-q4c2-5cw3?

Update org.openidentityplatform.openam:openam-core-rest to 16.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vg8-q4c2-5cw3 is resolved across your whole dependency graph.

How do I detect GHSA-2vg8-q4c2-5cw3 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.openidentityplatform.openam:openam-core-rest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2vg8-q4c2-5cw3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2vg8-q4c2-5cw3?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2vg8-q4c2-5cw3 can be triaged on real exposure rather than presence alone.

Is GHSA-2vg8-q4c2-5cw3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2vg8-q4c2-5cw3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2vg8-q4c2-5cw3?

GHSA-2vg8-q4c2-5cw3 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 30th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2vg8-q4c2-5cw3?

GHSA-2vg8-q4c2-5cw3 is classified as CWE-90 (CWE-90). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2vg8-q4c2-5cw3 published, and has it been updated?

GHSA-2vg8-q4c2-5cw3 was published on June 22, 2026 and was last updated on June 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-2vg8-q4c2-5cw3 — openam-core-rest

GHSA-2vg8-q4c2-5cw3 is a CWE-90 vulnerability in org.openidentityplatform.openam:openam-core-rest. A fix is available for org.openidentityplatform.openam:openam-core-rest — see the affected versions and patch details below.

OpenAM has LDAP Injection via `_queryId` Parameter

Also known asCVE-2026-41573

Published

Jun 22, 2026

Updated

Jun 22, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2vg8-q4c2-5cw3.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕org.openidentityplatform.openam:openam-core-rest

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

OpenAM (Open Identity Platform) is an open-source IAM platform providing SSO, OAuth2, SAML, and OpenID Connect capabilities. The CREST REST API layer exposes user query endpoints under /json/{realm}/users. In IdentityResourceV1.queryCollection(), the HTTP query parameter _queryId is passed to a CrestQuery object with escapeQueryId explicitly set to false, bypassing the escape protection introduced as part of the CVE-2021-29156 fix. The unescaped value flows directly to DJLDAPv3Repo.getFilter() where it is concatenated into an LDAP filter string without sanitization, enabling authenticated attackers to inject arbitrary LDAP metacharacters for user enumeration and blind LDAP injection.

Affected Endpoint

Endpoint	Auth Required	Injection Parameter
`GET /openam/json/{realm}/users?_queryId=<INJECTION>`	SSO Token	`_queryId`
`GET /openam/json/{realm}/groups?_queryId=<INJECTION>`	SSO Token (TBD)	`_queryId`

Background: CVE-2021-29156

CVE-2021-29156 was a pre-authentication LDAP injection in OpenAM's Webfinger endpoint, where user-supplied input reached DJLDAPv3Repo.getFilter() unescaped. The fix introduced the escapeQueryId flag in CrestQuery (defaulting to true) and added Filter.escapeAssertionValue() in the filter-building path:

Credit

Discovered by JD-Security SHENYI Team

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.openidentityplatform.openam:openam-core-rest`	all versions	16.1.1`org.openidentityplatform.openam:openam-core-rest:16.1.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.openidentityplatform.openam:openam-core-rest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.openidentityplatform.openam:openam-core-rest to 16.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2vg8-q4c2-5cw3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2vg8-q4c2-5cw3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2vg8-q4c2-5cw3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

OpenAM (Open Identity Platform) is an open-source IAM platform providing SSO, OAuth2, SAML, and OpenID Connect capabilities. The CREST REST API layer exposes user query endpoints under `/json/{realm}/users`. In `IdentityResourceV1.queryCollection()`, the HTTP query parameter `_queryId` is passed to a `CrestQuery` object with `escapeQueryId` **explicitly set to `false`**, bypassing the escape protection introduced as part of the CVE-2021-29156 fix. The unescaped value flows directly to `DJLDAPv3Repo.getFilter()` where it is concatenated into an LDAP filter string without sanitization, enabling

O3 Security · Impact-Aware SCA

Is GHSA-2vg8-q4c2-5cw3 in your dependencies?

O3 Security finds GHSA-2vg8-q4c2-5cw3 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works