Vulnerability Database · Maven · Package report

org.mapdb:mapdb: vulnerability history, versions and safety

org.mapdb:mapdb 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.mapdb:mapdb 3.1.0 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Not enough data

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

  • Current release 3.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 195 packages i
  • Last release 33 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 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.mapdb:mapdb, 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
3.1.0 10 Jan 2024 none Apache-2.0 — Details →
3.0.10 31 Aug 2023 none Apache-2.0 — Details →
3.0.9 24 Nov 2022 none Apache-2.0 — Details →
3.0.8 08 Jan 2020 none Apache-2.0 — Details →
3.0.7 28 May 2018 none Apache-2.0 — Details →
3.0.6 14 May 2018 none Apache-2.0 — Details →
3.0.5 08 Jul 2017 none Apache-2.0 — Details →
3.0.4 21 Apr 2017 none Apache-2.0 — Details →
3.0.3 12 Jan 2017 none Apache-2.0 — Details →
3.0.2 19 Sep 2016 none Apache-2.0 — Details →
3.0.1 17 Jul 2016 none Apache-2.0 — Details →
3.0.0 29 Jun 2016 none Apache-2.0 — Details →
3.0.0-RC2 19 Jun 2016 none Apache-2.0 — Details →
3.0.0-RC1 06 Jun 2016 none Apache-2.0 — Details →
3.0.0-beta5 23 May 2016 none Apache-2.0 — Details →
3.0.0-beta4 18 May 2016 none Apache-2.0 — Details →
3.0.0-beta3 08 May 2016 none Apache-2.0 — Details →
3.0.0-beta2 30 Apr 2016 none Apache-2.0 — Details →
3.0.0-beta1 28 Apr 2016 none Apache-2.0 — Details →
3.0.0-M6 23 Apr 2016 none Apache-2.0 — Details →
3.0.0-M5 13 Apr 2016 none Apache-2.0 — Details →
3.0.0-M4 28 Mar 2016 none Apache-2.0 — Details →
3.0.0-M3 10 Mar 2016 none Apache-2.0 — Details →
2.0-beta13 17 Feb 2016 none Apache-2.0 — Details →
1.0.9 15 Feb 2016 none Apache-2.0 — Details →
3.0.0-M2 12 Feb 2016 none Apache-2.0 — Details →
3.0.0-M1 20 Jan 2016 none Apache-2.0 — Details →
2.0-beta12 25 Nov 2015 none Apache-2.0 — Details →
2.0-beta11 18 Nov 2015 none Apache-2.0 — Details →
2.0-beta10 30 Oct 2015 none Apache-2.0 — Details →
2.0-beta8 28 Sep 2015 none Apache-2.0 — Details →
2.0-beta7 16 Sep 2015 none Apache-2.0 — Details →
2.0-beta6 18 Aug 2015 none Apache-2.0 — Details →
2.0-beta5 12 Aug 2015 none Apache-2.0 — Details →
2.0-beta4 03 Aug 2015 none Apache-2.0 — Details →
2.0-beta3 22 Jul 2015 none Apache-2.0 — Details →
2.0-beta2 09 Jul 2015 none Apache-2.0 — Details →
1.0.8 08 Jul 2015 none Apache-2.0 — Details →
2.0-beta1 28 Jun 2015 none Apache-2.0 — Details →
2.0-alpha3 16 Jun 2015 none Apache-2.0 — Details →
2.0-alpha2 29 Apr 2015 none Apache-2.0 — Details →
1.0.7 19 Feb 2015 none Apache-2.0 — Details →
2.0-alpha1 25 Jan 2015 none Apache-2.0 — Details →
1.0.6 07 Aug 2014 none Apache-2.0 — Details →
1.0.5 15 Jul 2014 none Apache-2.0 — Details →
1.0.4 26 Jun 2014 none Apache-2.0 — Details →
1.0.3 08 Jun 2014 none Apache-2.0 — Details →
1.0.2 02 Jun 2014 none Apache-2.0 — Details →
1.0.1 04 May 2014 none Apache-2.0 — Details →
1.0.0 27 Apr 2014 none Apache-2.0 — Details →
0.9.13 16 Apr 2014 none Apache-2.0 — Details →
0.9.12 15 Apr 2014 none Apache-2.0 — Details →
0.9.11 24 Mar 2014 none Apache-2.0 — Details →
0.9.10 18 Feb 2014 none Apache-2.0 — Details →
0.9.9 29 Jan 2014 none Apache-2.0 — Details →
0.9.8 30 Dec 2013 none Apache-2.0 — Details →
0.9.7 28 Oct 2013 none Apache-2.0 — Details →
0.9.6 27 Sep 2013 none Apache-2.0 — Details →
0.9.5 26 Aug 2013 none Apache-2.0 — Details →
0.9.4 09 Aug 2013 none Apache-2.0 — Details →
0.9.3 02 Jun 2013 none Apache-2.0 — Details →
0.9.2 19 May 2013 none Apache-2.0 — Details →
0.9.1 14 Apr 2013 none Apache-2.0 — Details →
0.9.0 01 Apr 2013 none Apache-2.0 — Details →

All 64 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.mapdb:mapdb

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.mapdb:mapdb

Is org.mapdb:mapdb safe to use?

Vulert has no vulnerabilities on record for org.mapdb:mapdb 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.mapdb:mapdb's Vulert package health score?

Vulert scores org.mapdb:mapdb 76/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.mapdb:mapdb affected?

No. 3.1.0, 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.mapdb:mapdb should I use?

3.1.0 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.mapdb:mapdb have?

0 vulnerabilities are recorded for org.mapdb:mapdb 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.mapdb:mapdb vulnerabilities disclosed?

0 vulnerabilities were recorded for org.mapdb:mapdb 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.mapdb:mapdb 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.mapdb:mapdb for upcoming vulnerabilities?

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