Apache HBase vulnerabilities: known CVEs & security history
Apache · Database · 5 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Apache HBase release lines — 5 in total. A CVE here doesn't mean your version is affected — check Apache HBase's current status and the safe version to run.
Known Apache HBase CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2018-8025 | high | 8.1 | 2% | 2018 |
| CVE-2019-15544 | high | 7.5 | 4% | 2019 |
| CVE-2019-0212 | high | 7.5 | 4% | 2019 |
| CVE-2015-1836 | high | 7.3 | 7% | 2015 |
| CVE-2013-2193 | medium | 4.3 | 1% | 2014 |
Is my Apache HBase version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Apache HBase version → · Monitor Apache HBase for new CVEs →
Apache HBase vulnerabilities — frequently asked
How many known vulnerabilities does Apache HBase have?
IsItPatched tracks 5 CVEs for Apache HBase. 0 are critical-severity and 4 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Apache HBase have any actively-exploited vulnerabilities?
None of Apache HBase's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Apache HBase vulnerability?
Among tracked issues, CVE-2018-8025 (HIGH, CVSS 8.1) ranks highest — a CWE-362 weakness.
Is Apache HBase safe to use?
It depends on the version. The latest supported Apache HBase release (2.6.6) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Apache HBase security status · Apache HBase end-of-life · actively-exploited CVEs. Always verify against Apache's advisories — see our disclaimer.