How severe is GHSA-85rw-g4f4-jprr?

No CVSS score has been assigned to GHSA-85rw-g4f4-jprr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-85rw-g4f4-jprr?

GHSA-85rw-g4f4-jprr affects the following packages: org.apache.directory.api:api-ldap-client-api (Maven). Ecosystems affected: Maven.

How do I fix GHSA-85rw-g4f4-jprr?

Update org.apache.directory.api:api-ldap-client-api to 2.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-85rw-g4f4-jprr is resolved across your whole dependency graph.

How do I detect GHSA-85rw-g4f4-jprr in my Maven dependencies?

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

How do I mitigate GHSA-85rw-g4f4-jprr 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.

Is GHSA-85rw-g4f4-jprr actively exploited in the wild?

No public exploit code has been indexed for GHSA-85rw-g4f4-jprr 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-85rw-g4f4-jprr?

GHSA-85rw-g4f4-jprr has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 16th 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-85rw-g4f4-jprr?

GHSA-85rw-g4f4-jprr is classified as CWE-297 (CWE-297). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-85rw-g4f4-jprr published, and has it been updated?

GHSA-85rw-g4f4-jprr was published on June 1, 2026 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-85rw-g4f4-jprr: api-ldap-client-api

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-85rw-g4f4-jprr.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.directory.api:api-ldap-client-api

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

It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate matches the intended LDAP hostname. While the underlying code validates the certificate chain against a trusted authority, the absence of endpoint identification allows a valid certificate issued for an entirely unrelated host to be improperly accepted. This oversight leaves the connection highly vulnerable to server impersonation and complete connection compromise.

The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP client implementation.

The attacker requires MITM capability on the network to exploit this vulnerability. This attacker must be able to present a certificate trusted by the client's configured trust store.

The hostname verification has been enforced in the new version of the LDAP API

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.directory.api:api-ldap-client-api`	≥ 2.0.0&&< 2.1.8	2.1.8`org.apache.directory.api:api-ldap-client-api:2.1.8`

Affected Products

1 product · 1 configurations

Application

directory ldap apiapache

≥ 2.0.0 && < 2.1.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.directory.api:api-ldap-client-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.directory.api:api-ldap-client-api to 2.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-85rw-g4f4-jprr 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.

Frequently Asked Questions

It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate matches the intended LDAP hostname. While the underlying code validates the certificate chain against a trusted authority, the absence of endpoint identification allows a valid certificate issued for an entirely unrelated host to be improperly accepted. This oversight leaves the connection highly vulnerable to server impersonation and complete connection compromise. The root cause of this vulnerability lies in the incomplete TLS server identity verification within the LDAP clien

O3 Security · Impact-Aware SCA

Is GHSA-85rw-g4f4-jprr in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

GHSA-85rw-g4f4-jprr — api-ldap-client-api