Vulnerability Database · Maven · Package report

org.apache.derby:derby: vulnerability history, versions and safety

org.apache.derby:derby is a package in the Maven ecosystem. Vulert records 7 vulnerabilities for it across 25 releases, from May 2022 to Nov 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded C2 H1 M4
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.derby:derby 10.17.1.0 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Not enough data

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

  • Current release 10.17.1.0 — unaffected i
  • Vulnerabilities on record 7 over 1 year · 0 in the last year i
  • Latest disclosure 20 Nov 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 261 packages i
  • Last release 35 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.derby:derby, 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
10.17.1.0 10 Nov 2023 none Apache-2.0 — Details →
10.16.1.1 14 Jun 2022 none Apache-2.0 — Details →
10.15.2.0 22 Feb 2020 none Apache-2.0 — Details →
10.15.1.3 10 Mar 2019 none Apache-2.0 — Details →
10.14.2.0 03 May 2018 C1 Apache-2.0 Yes Details →
10.14.1.0 14 Oct 2017 C1 M1 Apache-2.0 Yes Details →
10.13.1.1 27 Oct 2016 C1 M1 Apache-2.0 Yes Details →
10.12.1.1 11 Oct 2015 C1 M1 Apache-2.0 Yes Details →
10.11.1.1 27 Aug 2014 C2 M1 Apache-2.0 Yes Details →
10.10.2.0 16 Apr 2014 C2 M1 Apache-2.0 Yes Details →
10.10.1.1 16 Apr 2013 C2 M1 Apache-2.0 Yes Details →
10.8.3.0 15 Jan 2013 C2 M1 Apache-2.0 Yes Details →
10.9.1.0 26 Jun 2012 C2 M1 Apache-2.0 Yes Details →
10.8.2.2 25 Oct 2011 C2 M1 Apache-2.0 Yes Details →
10.8.1.2 29 Apr 2011 C2 M1 Apache-2.0 Yes Details →
10.7.1.1 14 Dec 2010 C2 M1 Apache-2.0 Yes Details →
10.6.2.1 12 Oct 2010 C2 M1 Apache-2.0 Yes Details →
10.6.1.0 18 May 2010 C2 M1 Apache-2.0 Yes Details →
10.5.3.0_1 07 Oct 2009 C2 M2 Apache-2.0 Yes Details →
10.5.3.0 26 Aug 2009 C2 M2 — Yes Details →
10.4.2.0 08 Sep 2008 C2 M2 — Yes Details →
10.4.1.3 25 Apr 2008 C2 H1 M2 — Yes Details →
10.3.2.1 11 Dec 2007 C2 H1 M2 — Yes Details →
10.3.1.4 16 Aug 2007 C2 H1 M2 — Yes Details →
10.2.2.0 22 Dec 2006 C2 H1 M1 — Yes Details →
10.2.1.6 07 Oct 2006 C2 H1 M1 — Yes Details →
10.1.3.1 09 Jul 2006 C2 H1 M2 — Yes Details →
10.1.2.1 31 Jan 2006 C2 H1 M2 — Yes Details →
10.1.1.0 22 Nov 2005 C2 M3 — Yes 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

  • 2022 6
  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.derby:derby

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →

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

Is org.apache.derby:derby safe to use?

Vulert records 7 vulnerabilities for org.apache.derby:derby in Maven: 2 critical, 1 high, 4 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.derby:derby's Vulert package health score?

Vulert scores org.apache.derby:derby 75/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.derby:derby affected?

No. 10.17.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.apache.derby:derby should I use?

10.17.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.apache.derby:derby have?

7 vulnerabilities are recorded for org.apache.derby:derby in the Maven ecosystem: 2 critical, 1 high, 4 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.derby:derby vulnerabilities disclosed?

0 vulnerabilities were recorded for org.apache.derby:derby in the last 12 months, and the oldest entry in this database dates to 01 May 2022. 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.derby:derby 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.derby:derby for upcoming vulnerabilities?

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