# CVE-2026-49326: Apache HBase: Missing scanner instance owner check in thrift delegation service

> Attackers can read data from or close scanners opened by other users due to missing owner checks in HBase thrift/rest services.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-4hqf-vmxx-hj9h

## What is CVE-2026-49326?

CVE-2026-49326 is a medium-severity missing authorization vulnerability in Apache HBase, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

This issue affects Apache HBase:from 3.0.0-alpha-1 through 3.0.0-beta-1, from 2.6.0 through 2.6.5, from 2.5.0 through 2.5.14, through 2.4.*.

Users are recommended to upgrade to version 3.0.0-beta-2, 2.6.6 and 2.5.15, which fixes the issue.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-49326?

It affects 1 product.


Products: Apache Hbase.

## How do I fix CVE-2026-49326?

No fix has been published for CVE-2026-49326 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-49326 being exploited?

There is no known exploitation of CVE-2026-49326 in the wild and no public exploit code.

## Other vulnerabilities in Apache HBase

- [CVE-2018-8025](https://insights.sbomify.com/CVE-2018-8025/): Race condition in org.apache.hbase:hbase-thrift (high 8.1)
- [CVE-2019-15544](https://insights.sbomify.com/CVE-2019-15544/): Uncontrolled memory consumption in protobuf (high 7.5)
- [CVE-2019-0212](https://insights.sbomify.com/CVE-2019-0212/): Improper Authorization in org.apache.hbase:hbase (high 7.5)
- [CVE-2015-1836](https://insights.sbomify.com/CVE-2015-1836/): High severity vulnerability that affects org.apache.hbase:hbase (high 7.3)
- [CVE-2013-2193](https://insights.sbomify.com/CVE-2013-2193/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49326 and fix it if it is affected.

What it is: CVE-2026-49326 is a medium-severity missing authorization vulnerability in Apache HBase, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49326 in the wild and no public exploit code.

Affected product: Apache HBase. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49326/ (Markdown: https://insights.sbomify.com/CVE-2026-49326/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49326
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49326
- OSV: https://osv.dev/vulnerability/CVE-2026-49326

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49326/
Summaries are generated and may contain mistakes; the official description above is the record.