Vulnerability Database · Maven · Package report

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

org.apache.zeppelin:zeppelin is a package in the Maven ecosystem. Vulert records 8 vulnerabilities for it across 14 releases, from Apr 2019 to Jul 2023. 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 H3 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.zeppelin:zeppelin 0.12.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.12.1 — unaffected i
  • Vulnerabilities on record 8 over 4 years · 0 in the last year i
  • Latest disclosure 06 Jul 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Last release 4 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.zeppelin:zeppelin, 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
0.12.1 23 May 2026 none Apache-2.0 — Details →
0.12.0 28 Dec 2024 none Apache-2.0 — Details →
0.11.2 18 Aug 2024 none Apache-2.0 — Details →
0.11.1 29 Mar 2024 none Apache-2.0 — Details →
0.11.0 16 Feb 2024 none Apache-2.0 — Details →
0.10.1 28 Feb 2022 none Apache-2.0 — Details →
0.10.0 18 Aug 2021 none Apache-2.0 — Details →
0.9.0 20 Dec 2020 C1 H1 M1 Apache-2.0 Yes Details →
0.9.0-preview2 23 Jul 2020 C1 H1 M1 Apache-2.0 Yes Details →
0.9.0-preview1 23 Mar 2020 C1 H1 M1 Apache-2.0 Yes Details →
0.8.2 26 Sep 2019 C1 H1 M2 Apache-2.0 Yes Details →
0.8.1 17 Jan 2019 C1 H1 M3 Apache-2.0 Yes Details →
0.8.0 24 Jun 2018 C1 H1 M3 Apache-2.0 Yes Details →
0.7.3 18 Sep 2017 C1 H2 M4 Apache-2.0 Yes Details →
0.7.2 09 Jun 2017 C1 H3 M4 Apache-2.0 Yes Details →
0.7.1 28 Mar 2017 C1 H3 M4 Apache-2.0 Yes Details →
0.7.0 02 Feb 2017 C1 H3 M4 Apache-2.0 Yes Details →
0.6.2 12 Oct 2016 C1 H3 M4 Apache-2.0 Yes Details →
0.6.1 12 Aug 2016 C1 H3 M4 Apache-2.0 Yes Details →
0.6.0 27 Jun 2016 C1 H3 M4 Apache-2.0 Yes Details →
0.5.0-incubating 11 Jul 2015 C1 H3 M4 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 3
  • 2021 3
  • 2022 1
  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.zeppelin:zeppelin

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

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

Vulert records 8 vulnerabilities for org.apache.zeppelin:zeppelin in Maven: 1 critical, 3 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.zeppelin:zeppelin's Vulert package health score?

Vulert scores org.apache.zeppelin:zeppelin 68/100, which reads as usable, but worth attention. 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.zeppelin:zeppelin affected?

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

0.12.1 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.zeppelin:zeppelin have?

8 vulnerabilities are recorded for org.apache.zeppelin:zeppelin in the Maven ecosystem: 1 critical, 3 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.zeppelin:zeppelin vulnerabilities disclosed?

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

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