Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vendor requires an authenticated/trusted Metastore caller so PR:L not PR:N; low-complexity injection; confidentiality limited to partition metadata (C:L) while wrong-partition truncate/drop drives I:H/A:H.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
6DescriptionCVE.org
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.
Articles & Coverage 2
AnalysisAI
SQL injection in the Apache Hive Metastore (versions 4.0.0 through 4.2.0) lets a caller who can invoke partition-name Metastore RPCs manipulate the generated WHERE clause so operations intended for one partition match additional rows in the same table. Because client-supplied partition names are concatenated into direct-SQL statements instead of bound as parameters, a crafted name containing a single quote can redirect reads, statistics updates, truncate/drop targets, and file-metadata cache operations to unintended partitions. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires (1) the ability to invoke Hive Metastore partition-name RPCs (e.g., getPartitionsByNames, partition column-statistics updates, truncate/drop, file-metadata cache operations) against a target table the caller can reference - the vendor states this needs an authenticated or network-trusted caller, so it is not truly unauthenticated despite the PR:N in the supplied CVSS vector; (2) metastore.try.direct.sql enabled, which is the default (metastore.try.direct.sql=true); and (3) a crafted PART_NAME containing a single quote and injected SQL passed through the direct-SQL helpers (DirectSqlUpdatePart.quoteString / MetaStoreDirectSql.getPartitionsByNames). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals conflict and must be reconciled before prioritization. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: 4.2.1 - upgrade the Hive Metastore server to 4.2.1, which replaces the vulnerable string-concatenated partition-name queries with bound parameters (fix commit https://github.com/apache/hive/commit/ca64f08a8e43db9845b47d5fa2e96f7fdea7288e; advisory https://lists.apache.org/thread/6d56mk501fp4f8cb5wvrpj2jwd9knt05). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all Hive Metastore deployments and confirm which run versions 4.0.0 through 4.2.0; flag these systems as requiring immediate remediation. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Apache Hive
View allServer-side request forgery in Apache Hive versions 2.1.0 through 4.2.0 lets an authenticated user with CREATE TABLE rig
Authentication bypass in Apache HiveServer2 4.0.0-4.2.0 allows unauthenticated network attackers to impersonate any Hive
Same weakness CWE-94 – Code Injection
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-65396
GHSA-5555-2x3r-gmgx