# CVE-2026-49845: Apache Hive: SQL Injection vulnerability in HiveMetaStore partition-name direct-SQL paths

> Authenticated users can inject SQL via crafted partition names in Apache Hive Metastore to read or modify unintended partition metadata.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-5555-2x3r-gmgx

## What is CVE-2026-49845?

CVE-2026-49845 is a critical SQL injection vulnerability in Apache Hive, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection in Hive Metastore direct SQL partition-name resolution in Apache Hive before 4.2.1 on all platforms allows authenticated users with access to Hive Metastore APIs to read, modify, or affect unintended partition metadata (including statistics updates, truncation targets, and file-metadata cache operations) via crafted partition names in metastore RPC requests when direct SQL is enabled (the default). Users are recommended to upgrade to version 4.2.1, which fixes this issue.

Details about the issue:
Several Hive Metastore RPCs resolve partitions by full partition name (PART_NAME) through direct-SQL helpers. In those paths, client-supplied partition names are embedded into SQL using string concatenation (DirectSqlUpdatePart.quoteString() → '...') instead of bind parameters. A partition name containing a single quote (and crafted SQL) can alter the generated WHERE clause so that lookups intended for one partition match additional rows. That can affect reads, stats updates, truncate targets, metadata-cache targets, and related operations when metastore.try.direct.sql is enabled (default: true). An authenticated or network-trusted caller with the ability to invoke Hive Metastore partition-name APIs against a target table (directly or via Hive/other clients), when direct SQL is enabled can perform this attack. Also, the impact is mainly within table & partition targeting (read/update/truncate/drop/cache the wrong partitions in a table they can reference), not arbitrary cross-database access via this bug alone.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Apache Hive.

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

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

## Is CVE-2026-49845 being exploited?

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

## Other vulnerabilities in Apache Hive

- [CVE-2018-21234](https://insights.sbomify.com/CVE-2018-21234/): Deserialization of Untrusted Data in Jodd (critical 9.8)
- [CVE-2026-55976](https://insights.sbomify.com/CVE-2026-55976/): Apache Hive: SSRF vulnerability in Hive Avro Serde due to Insufficient input validation on avro.schema.url (critical 9.1)
- [CVE-2018-1282](https://insights.sbomify.com/CVE-2018-1282/): SQL Injection in hive-jdbc (critical 9.1)
- [CVE-2022-41137](https://insights.sbomify.com/CVE-2022-41137/): Apache Hive: Deserialization of untrusted data when fetching partitions from the Metastore (high 8.3)
- [CVE-2015-7521](https://insights.sbomify.com/CVE-2015-7521/): High severity vulnerability that affects org.apache.hive:hive, org.apache.hive:hive-exec, and org.apache.hive:hive-service (high 8.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49845 is a critical SQL injection vulnerability in Apache Hive, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49845 in the wild and no public exploit code.

Affected product: Apache Hive. 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-49845/ (Markdown: https://insights.sbomify.com/CVE-2026-49845/index.md)
```

## Sources

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

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