Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, IdentityResourceV1.queryCollection() passes the _queryId parameter from /json/{realm}/users to CrestQuery with escapeQueryId disabled, bypassing protection added for CVE-2021-29156. The unescaped value reaches DJLDAPv3Repo.getFilter(), where it is concatenated into an LDAP filter, allowing an authenticated attacker to inject LDAP metacharacters for user enumeration and blind LDAP injection. This issue is fixed in version 16.1.1.
CVE-2026-41573
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
June 22, 2026
Last Modified
September 15, 2026
Advisory Details (3)
Auto-updated Sep 15, 202616.1.1
Patch available: OpenIdentityPlatform/OpenAM 16.1.1
https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.1.1commit d3d86c951a4c (OpenIdentityPlatform/OpenAM)
Fix landed in OpenIdentityPlatform/OpenAM commit d3d86c951a4c — awaiting tagged release
https://github.com/OpenIdentityPlatform/OpenAM/commit/d3d86c951a4c3c353719b761ea0b4be80f9dd241OpenAM LDAP Injection via `_queryId` Parameter · Advisory · OpenIdentityPlatform/OpenAM · GitHub
https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-2vg8-q4c2-5cw3Vendor Advisories for CVE-2026-41573(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.openidentityplatform.openam:openam-core-rest | 14.5.2 ... 16.1.0 (40 versions) | 16.1.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 11:15 UTCEG score recompute
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 13:34 UTCEG score recompute
- 2026-09-15 12:53 UTCEG score recompute
- 2026-09-15 10:29 UTCEG score recompute
- 2026-09-15 10:03 UTCEG score recompute▲ 7.10
- 2026-09-15 10:02 UTCMITRE cvelistV5CVSS v3 → 7.1 · CVSS v4 → 7.1
- 2026-08-01 04:29 UTCEG score recompute
- 2026-07-26 15:58 UTCEG score recompute
- 2026-07-23 03:11 UTCEG score recompute
- 2026-06-22 20:36 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-41573?
When was CVE-2026-41573 disclosed?
Is CVE-2026-41573 actively exploited?
What is the CVSS score of CVE-2026-41573?
How do I remediate CVE-2026-41573?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41573
Is Your Infrastructure Affected by CVE-2026-41573?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.