Vulnerability Database · Maven · Package report

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

org.apache.druid:druid is a package in the Maven ecosystem. Vulert records 8 vulnerabilities for it across 40 releases, from Jun 2021 to Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C1 H2 M4 L1
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 26 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.apache.druid:druid 38.0.0 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 38.0.0 — unaffected i
  • Vulnerabilities on record 8 over 4 years · 1 in the last year i
  • Latest disclosure 26 Nov 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 14,091 i
  • OpenSSF scorecard 5/10 i
  • Last release this month 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.apache.druid:druid, 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
38.0.0 24 Sep 2026 none Apache-2.0 — Details →
37.0.0 28 Apr 2026 none Apache-2.0 — Details →
36.0.0 02 Feb 2026 none Apache-2.0 — Details →
35.0.1 05 Dec 2025 none Apache-2.0 — Details →
35.0.0 28 Oct 2025 none Apache-2.0 — Details →
34.0.0 04 Aug 2025 C1 Apache-2.0 Yes Details →
33.0.0 18 Apr 2025 C1 Apache-2.0 Yes Details →
32.0.1 13 Mar 2025 C1 Apache-2.0 Yes Details →
31.0.2 13 Mar 2025 C1 Apache-2.0 Yes Details →
32.0.0 31 Jan 2025 C1 Apache-2.0 Yes Details →
31.0.1 19 Dec 2024 M1 Apache-2.0 Yes Details →
31.0.0 18 Oct 2024 M1 Apache-2.0 Yes Details →
30.0.1 08 Sep 2024 M1 Apache-2.0 Yes Details →
30.0.0 08 Jun 2024 M1 L1 Apache-2.0 Yes Details →
29.0.1 21 Mar 2024 M1 L1 Apache-2.0 Yes Details →
29.0.0 13 Feb 2024 M1 L1 Apache-2.0 Yes Details →
28.0.1 10 Dec 2023 M1 L1 Apache-2.0 Yes Details →
28.0.0 06 Nov 2023 M1 L1 Apache-2.0 Yes Details →
27.0.0 05 Aug 2023 M1 L1 Apache-2.0 Yes Details →
26.0.0 19 May 2023 M1 L1 Apache-2.0 Yes Details →
25.0.0 22 Dec 2022 M1 L1 Apache-2.0 Yes Details →
24.0.2 25 Nov 2022 M1 L1 Apache-2.0 Yes Details →
24.0.1 07 Nov 2022 M1 L1 Apache-2.0 Yes Details →
24.0.0 10 Sep 2022 M1 L1 Apache-2.0 Yes Details →
0.23.0 15 Jun 2022 M1 L1 Apache-2.0 Yes Details →
0.22.1 11 Dec 2021 M3 L1 Apache-2.0 Yes Details →
0.22.0 16 Sep 2021 M3 L1 Apache-2.0 Yes Details →
0.21.1 02 Jun 2021 M3 L1 Apache-2.0 Yes Details →
0.21.0 16 Apr 2021 M3 L1 Apache-2.0 Yes Details →
0.20.2 25 Mar 2021 M3 L1 Apache-2.0 Yes Details →
0.20.1 27 Jan 2021 H1 M3 L1 Apache-2.0 Yes Details →
0.20.0 09 Oct 2020 H2 M3 L1 Apache-2.0 Yes Details →
0.19.0 13 Jul 2020 H2 M3 L1 Apache-2.0 Yes Details →
0.18.1 06 May 2020 H2 M3 L1 Apache-2.0 Yes Details →
0.18.0 16 Apr 2020 H2 M3 L1 Apache-2.0 Yes Details →
0.17.1 31 Mar 2020 H2 M3 L1 Apache-2.0 Yes Details →
0.17.0 22 Jan 2020 H2 M4 L1 Apache-2.0 Yes Details →
0.16.1-incubating 07 Dec 2019 H2 M3 L1 Apache-2.0 Yes Details →
0.16.0-incubating 18 Sep 2019 H2 M3 L1 Apache-2.0 Yes Details →
0.15.1-incubating 06 Aug 2019 H2 M3 L1 Apache-2.0 Yes Details →
0.15.0-incubating 20 Jun 2019 H2 M3 L1 Apache-2.0 Yes Details →
0.14.2-incubating 16 May 2019 H2 M3 L1 Apache-2.0 Yes Details →
0.14.1-incubating 01 May 2019 H2 M3 L1 Apache-2.0 Yes Details →
0.14.0-incubating 02 Apr 2019 H2 M3 L1 Apache-2.0 Yes Details →
0.13.0-incubating 02 Dec 2018 H2 M3 L1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2022 3
  • 2024 1
  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.druid:druid

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 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.druid:druid

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

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

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

No. 38.0.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.druid:druid should I use?

38.0.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.druid:druid have?

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

1 vulnerability was recorded for org.apache.druid:druid in the last 12 months, and the oldest entry in this database dates to 16 Jun 2021. 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.druid:druid 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.druid:druid for upcoming vulnerabilities?

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