Vulnerability Database · Maven · Package report

org.apache.directory.server:apacheds-core-api: vulnerability history, versions and safety

org.apache.directory.server:apacheds-core-api is a package in the Maven ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Maven ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.apache.directory.server:apacheds-core-api 2.0.0.AM27 i

Updated on 23 Oct 2026

Good news: 2.0.0.AM27, the version you would install today, has no known vulnerabilities.

Package health score 72/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Not enough data

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

  • Current release 2.0.0.AM27 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 64 packages i
  • Last release 36 months ago 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.server:apacheds-core-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.0.0.AM27 09 Oct 2023 none Apache-2.0 — Details →
2.0.0.AM26 28 Feb 2020 none Apache-2.0 — Details →
2.0.0.AM25 14 Aug 2018 none Apache-2.0 — Details →
2.0.0-M24 03 Jun 2017 none Apache-2.0 — Details →
2.0.0-M23 16 Jul 2016 none Apache-2.0 — Details →
2.0.0-M22 22 Jun 2016 none Apache-2.0 — Details →
2.0.0-M21 18 Dec 2015 none Apache-2.0 — Details →
2.0.0-M20 28 Apr 2015 none Apache-2.0 — Details →
2.0.0-M19 19 Nov 2014 none Apache-2.0 — Details →
2.0.0-M18 13 Nov 2014 none Apache-2.0 — Details →
2.0.0-M17 30 Jun 2014 none Apache-2.0 — Details →
2.0.0-M16 10 Mar 2014 none Apache-2.0 — Details →
2.0.0-M15 14 Aug 2013 none Apache-2.0 — Details →
2.0.0-M14 27 Jun 2013 none Apache-2.0 — Details →
2.0.0-M13 21 Jun 2013 none Apache-2.0 — Details →
2.0.0-M12 29 Apr 2013 none Apache-2.0 — Details →
2.0.0-M11 26 Feb 2013 none Apache-2.0 — Details →
2.0.0-M10 22 Jan 2013 none Apache-2.0 — Details →
2.0.0-M9 22 Dec 2012 none Apache-2.0 — Details →
2.0.0-M8 09 Oct 2012 none Apache-2.0 — Details →
2.0.0-M7 05 May 2012 none Apache-2.0 — Details →
2.0.0-M6 24 Feb 2012 none Apache-2.0 — Details →
2.0.0-M5 27 Jan 2012 none Apache-2.0 — Details →
2.0.0-M4 09 Jan 2012 none Apache-2.0 — Details →
2.0.0-M3 09 Sep 2011 none Apache-2.0 — Details →
2.0.0-M2 15 Aug 2011 none Apache-2.0 — Details →
2.0.0-M1 22 Jun 2011 none Apache-2.0 — Details →
1.5.7 02 Apr 2010 none Apache-2.0 — Details →
1.5.6 19 Mar 2010 none Apache-2.0 — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for org.apache.directory.server:apacheds-core-api

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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.server:apacheds-core-api

Is org.apache.directory.server:apacheds-core-api safe to use?

Vulert has no vulnerabilities on record for org.apache.directory.server:apacheds-core-api in Maven at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is org.apache.directory.server:apacheds-core-api's Vulert package health score?

Vulert scores org.apache.directory.server:apacheds-core-api 72/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.server:apacheds-core-api affected?

No. 2.0.0.AM27, 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.server:apacheds-core-api should I use?

2.0.0.AM27 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.server:apacheds-core-api have?

0 vulnerabilities are recorded for org.apache.directory.server:apacheds-core-api in the Maven ecosystem: 0 critical, 0 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.server:apacheds-core-api vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.directory.server:apacheds-core-api in the last 12 months. 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.server:apacheds-core-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.server:apacheds-core-api for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.directory.server:apacheds-core-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.