Apache HBase 1.7
Apache HBase 1.7
The Apache HBase 1.7 reached end of service life on Aug 9, 2022 — Apache HBase no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Apache HBase 1.7 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- hbase
- release
- 1.7
- product Label
- Apache HBase
- release Label
- 1.7
- codename
- lts
- latest Version
- 1.7.2
- release Date
- 2021-06-12
- maintained
- source Url
- https://endoflife.date/hbase
Lifecycle Dates
- End of Service Life
- Aug 9, 2022
- Last OEM Support
- Aug 9, 2022
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Apache HBase 1.7 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Apache HBase 1.7?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Apache HBase 1.7 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Apache HBase 1.7 Support: Frequently Asked Questions
Is the Apache HBase 1.7 still supported?
Apache HBase ended support for the Apache HBase 1.7 on Aug 9, 2022 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Apache HBase 1.7 end of service life (EOSL) date?
Apache HBase lists the end of service life for the Apache HBase 1.7 as Aug 9, 2022.
Can I keep using the Apache HBase 1.7 after its EOSL date?
Yes. EOSL means Apache HBase stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Apache HBase 1.7 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Apache HBase 1.7
2 published CVEs affect the Apache HBase 1.7, including 1 rated critical or high severity. Apache HBase no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2018-8025 | HIGH | 8.1 | Jun 27, 2018 | CVE-2018-8025 describes an issue in Apache HBase that affects the optional "Thrift 1" API server when running over HTTP. There is a race-condition which could lead to authenticated sessions being incorrectly applied to users, e.g. one authenticated user would be considered a different user or an unauthenticated user would be treated as an authenticated user. https://issues.apache.org/jira/browse/HBASE-20664 implements a fix for this issue. It has been fixed in versions: 1.2.6.1, 1.3.2.1, 1.4.5, |
| CVE-2026-49326 | MEDIUM | 6.5 | Jul 24, 2026 | Missing Authorization vulnerability in Apache HBase thrift and rest delegation service. A scan operation in thrift/rest service has 3 steps, open, fetch(possible multiple times), close. The open step will return an id which will be passed back to server for identifying the scanner instances stored at server side. We missed the owner check in fetch and close steps which means a user can fetch rows from the scanner which is opened by other users, and close scanners which belongs to other users. |