VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.directory.api:api-ldap-client-api: vulnerability history, versions and safety

org.apache.directory.api:api-ldap-client-api is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 15 releases, first recorded in Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 01 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.directory.api:api-ldap-client-api vulnerabilities

Vulert verdict on org.apache.directory.api:api-ldap-client-api 2.1.9 i

Updated on 23 Oct 2026

Good news: 2.1.9, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 2.1.9 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.1.9 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.1.9 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 01 Jun 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 5 packages i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.apache.directory.api:api-ldap-client-api, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.1.9 24 Sep 2026 none Apache-2.0 — Details →
2.1.8 27 May 2026 none Apache-2.0 — Details →
2.1.7 02 Aug 2024 H1 Apache-2.0 Yes Details →
2.1.6 01 Feb 2024 H1 Apache-2.0 Yes Details →
2.1.5 08 Oct 2023 H1 Apache-2.0 Yes Details →
2.1.4 18 Aug 2023 H1 Apache-2.0 Yes Details →
2.1.3 05 Apr 2023 H1 Apache-2.0 Yes Details →
2.1.2 10 Aug 2022 H1 Apache-2.0 Yes Details →
2.1.1 28 Jul 2022 H1 Apache-2.0 Yes Details →
2.1.0 25 Jun 2021 H1 Apache-2.0 Yes Details →
2.0.2 22 May 2021 H1 Apache-2.0 Yes Details →
2.0.1 21 Mar 2020 H1 Apache-2.0 Yes Details →
2.0.0 06 Nov 2019 H1 Apache-2.0 Yes Details →
2.0.0.AM4 05 Jun 2019 H1 Apache-2.0 Yes Details →
2.0.0.AM3 11 May 2019 H1 Apache-2.0 Yes Details →
1.0.3 17 Apr 2019 none Apache-2.0 — Details →
2.0.0.AM2 28 Aug 2018 H1 Apache-2.0 Yes Details →
2.0.0.AM1 15 Jul 2018 H1 Apache-2.0 Yes Details →
1.0.2 01 Jun 2018 none Apache-2.0 — Details →
1.0.1 30 Apr 2018 none Apache-2.0 — Details →
1.0.0 01 Jun 2017 none Apache-2.0 — Details →
1.0.0-RC2 26 Oct 2016 none Apache-2.0 — Details →
1.0.0-RC1 14 Jun 2016 none Apache-2.0 — Details →
1.0.0-M33 18 Dec 2015 none Apache-2.0 — Details →
1.0.0-M32 14 Oct 2015 none Apache-2.0 — Details →
1.0.0-M31 30 Jun 2015 none Apache-2.0 — Details →
1.0.0-M30 28 Apr 2015 none Apache-2.0 — Details →
1.0.0-M29 29 Mar 2015 none Apache-2.0 — Details →
1.0.0-M28 10 Jan 2015 none Apache-2.0 — Details →
1.0.0-M27 24 Dec 2014 none Apache-2.0 — Details →
1.0.0-M26 19 Nov 2014 none Apache-2.0 — Details →
1.0.0-M25 07 Nov 2014 none Apache-2.0 — Details →
1.0.0-M24 28 Jul 2014 none Apache-2.0 — Details →
1.0.0-M23 29 Jun 2014 none Apache-2.0 — Details →
1.0.0-M22 18 Apr 2014 none Apache-2.0 — Details →
1.0.0-M21 06 Mar 2014 none Apache-2.0 — Details →
1.0.0-M20 14 Aug 2013 none Apache-2.0 — Details →
1.0.0-M19 27 Jun 2013 none Apache-2.0 — Details →
1.0.0-M18 21 Jun 2013 none Apache-2.0 — Details →
1.0.0-M17 29 Apr 2013 none Apache-2.0 — Details →
1.0.0-M16 26 Feb 2013 none Apache-2.0 — Details →
1.0.0-M15 22 Jan 2013 none Apache-2.0 — Details →
1.0.0-M14 21 Dec 2012 none Apache-2.0 — Details →

All 43 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.directory.api:api-ldap-client-api

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-35563: Apache Directory LDAP API Server Certificate Verification Bypass 8.8 high 2.1.8 01 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

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

Is org.apache.directory.api:api-ldap-client-api safe to use?

Vulert records 1 vulnerabilities for org.apache.directory.api:api-ldap-client-api in Maven: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.apache.directory.api:api-ldap-client-api's Vulert package health score?

Vulert scores org.apache.directory.api:api-ldap-client-api 78/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.apache.directory.api:api-ldap-client-api affected?

No. 2.1.9, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.apache.directory.api:api-ldap-client-api should I use?

2.1.9 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.apache.directory.api:api-ldap-client-api have?

1 vulnerability is recorded for org.apache.directory.api:api-ldap-client-api in the Maven ecosystem: 0 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.apache.directory.api:api-ldap-client-api vulnerabilities disclosed?

1 vulnerability was recorded for org.apache.directory.api:api-ldap-client-api in the last 12 months, and the oldest entry in this database dates to 01 Jun 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.apache.directory.api:api-ldap-client-api are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.apache.directory.api:api-ldap-client-api for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.directory.api:api-ldap-client-api version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.