VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.hive:hive-jdbc: vulnerability history, versions and safety

org.apache.hive:hive-jdbc is a package in the Maven ecosystem. Vulert records 3 vulnerabilities for it across 28 releases, from Nov 2018 to May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 M2
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.

See all org.apache.hive:hive-jdbc vulnerabilities

Vulert verdict on org.apache.hive:hive-jdbc 4.2.1 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Not enough data

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

  • Current release 4.2.1 — unaffected i
  • Vulnerabilities on record 3 over 5 years · 0 in the last year i
  • Latest disclosure 03 May 2024 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 45 packages i
  • Last release 1 month 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.apache.hive:hive-jdbc, 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
4.2.1 10 Sep 2026 none Apache-2.0 — Details →
4.2.0 17 Nov 2025 none Apache-2.0 — Details →
4.1.0 19 Jul 2025 none Apache-2.0 — Details →
4.0.1 26 Sep 2024 none Apache-2.0 — Details →
2.3.10 05 May 2024 none Apache-2.0 — Details →
4.0.0 25 Mar 2024 none Apache-2.0 — Details →
4.0.0-beta-1 07 Aug 2023 M1 Apache-2.0 Yes Details →
4.0.0-alpha-2 07 Nov 2022 M1 Apache-2.0 Yes Details →
3.1.3 04 Apr 2022 none Apache-2.0 — Details →
4.0.0-alpha-1 24 Mar 2022 M1 Apache-2.0 Yes Details →
2.3.9 01 Jun 2021 none Apache-2.0 — Details →
2.3.8 08 Jan 2021 none Apache-2.0 — Details →
2.3.7 08 Apr 2020 none Apache-2.0 — Details →
3.1.2 22 Aug 2019 none Apache-2.0 — Details →
2.3.6 13 Aug 2019 none Apache-2.0 — Details →
2.3.5 16 May 2019 none Apache-2.0 — Details →
2.3.4 31 Oct 2018 none Apache-2.0 — Details →
3.1.1 24 Oct 2018 none Apache-2.0 — Details →
3.1.0 23 Jul 2018 none Apache-2.0 — Details →
3.0.0 21 May 2018 none Apache-2.0 — Details →
2.3.3 29 Mar 2018 M1 Apache-2.0 Yes Details →
2.3.2 09 Nov 2017 C1 M1 Apache-2.0 Yes Details →
2.3.1 20 Oct 2017 C1 M1 Apache-2.0 Yes Details →
2.2.0 25 Jul 2017 C1 M1 Apache-2.0 Yes Details →
2.3.0 18 Jul 2017 C1 M1 Apache-2.0 Yes Details →
1.2.2 03 Apr 2017 C1 M1 Apache-2.0 Yes Details →
2.1.1 29 Nov 2016 C1 M1 Apache-2.0 Yes Details →
2.1.0 17 Jun 2016 C1 M1 Apache-2.0 Yes Details →
2.0.1 28 May 2016 C1 M1 Apache-2.0 Yes Details →
2.0.0 10 Feb 2016 C1 M1 Apache-2.0 Yes Details →
1.2.1 19 Jun 2015 C1 M1 Apache-2.0 Yes Details →
1.2.0 15 May 2015 C1 M1 Apache-2.0 Yes Details →
1.0.1 14 May 2015 C1 M1 Apache-2.0 Yes Details →
1.1.1 14 May 2015 C1 M1 Apache-2.0 Yes Details →
1.1.0 19 Feb 2015 C1 M1 Apache-2.0 Yes Details →
1.0.0 30 Jan 2015 C1 M1 Apache-2.0 Yes Details →
0.14.0 09 Nov 2014 C1 M1 Apache-2.0 Yes Details →
0.13.1 02 Jun 2014 C1 M1 Apache-2.0 Yes Details →
0.13.0 15 Apr 2014 C1 M1 Apache-2.0 Yes Details →
0.12.0 10 Oct 2013 C1 M1 Apache-2.0 Yes Details →
0.11.0 13 May 2013 C1 M1 Apache-2.0 Yes Details →
0.10.0 19 Dec 2012 C1 M1 Apache-2.0 Yes Details →
0.9.0 28 Apr 2012 C1 M1 Apache-2.0 Yes Details →
0.8.1 26 Jan 2012 C1 M1 Apache-2.0 Yes Details →
0.8.0 13 Dec 2011 C1 M1 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

  • 2018 2
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.hive:hive-jdbc

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-1282: SQL Injection in hive-jdbc 9.1 critical 2.3.3 21 Nov 2018
Apache Hive Code Injection Vulnerability in org.apache.hive:hive-jdbc 6.6 medium 4.0.0 03 May 2024
CVE-2018-1314: Apache Hive JDBC 'EXPLAIN' Operation Authorization Bypass 4.3 medium 2.3.4 21 Nov 2018

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.hive:hive-jdbc

Is org.apache.hive:hive-jdbc safe to use?

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

Vulert scores org.apache.hive:hive-jdbc 82/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.hive:hive-jdbc affected?

No. 4.2.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.hive:hive-jdbc should I use?

4.2.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.hive:hive-jdbc have?

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

0 vulnerabilities were recorded for org.apache.hive:hive-jdbc in the last 12 months, and the oldest entry in this database dates to 21 Nov 2018. 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.hive:hive-jdbc 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.hive:hive-jdbc for upcoming vulnerabilities?

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