Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to HiveServer2 with DDL rights
-
DeliveryCREATE Avro table with malicious avro.schema.url
-
ExploitRun SELECT to trigger schema resolution
-
ExecutionHive fetches attacker URL as service identity
-
ImpactRead cloud metadata/internal services/local files
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated Hive session with CREATE TABLE (or equivalent DDL) privilege and network access to HiveServer2/Metastore; the attacker sets the avro.schema.url property on an Avro-SerDe table using an attacker-controlled URL (http/https/file/ftp scheme, e.g. targeting 169.254.169.254 or internal hosts), and the fetch triggers when that table is subsequently queried (the creator can query their own table; other users granted SELECT can also trigger it). External tables must typically be enabled - the default in most deployments. Limiting factors: exploitation is NOT unauthenticated despite the CVSS PR:N - a valid login plus DDL rights is mandatory; admin/superuser is not required; write access to the table LOCATION is not required; and the impact is a read-only server-side GET, so it exposes data rather than modifying it. In hardened clusters where untrusted users lack CREATE TABLE or where external tables are disabled, the path is closed. |
| Impact | The signals are mixed and should be weighed together. CVSS is 9.1 (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:N), but the vector's PR:N conflicts with the authoritative description and Apache's own access notes, which state a valid Hive login plus CREATE TABLE (DDL) privilege is required - verify with vendor, and treat this as an authenticated flaw rather than a fully unauthenticated one. EPSS is low (0.29%, 21st percentile) and there is no KEV listing and no public exploit identified, suggesting this is not currently subject to broad opportunistic exploitation. Against that, the technical impact is high: SSRF from a Hive service identity in cloud environments can harvest instance-metadata credentials, and the prerequisite (ordinary DDL rights, external tables enabled by default) is common in real deployments, so the practical barrier is low for any insider or compromised low-privilege account. Net: a genuine priority for multi-tenant or cloud-hosted Hive clusters where untrusted users hold CREATE TABLE, and lower urgency for tightly locked-down single-tenant installs; the high CVSS should be tempered by the low EPSS and the authentication requirement, not taken at face value. |
| Exploit ScenarioDerived | An analyst holding an ordinary Hive account with CREATE TABLE rights on a cloud-hosted cluster creates an Avro external table with avro.schema.url set to http://169.254.169.254/latest/meta-data/iam/security-credentials/, then runs a SELECT against it. Hive resolves the schema by fetching that URL under the service identity and surfaces or logs the cloud metadata response, handing the attacker instance credentials or internal service data. No public exploit is identified at time of analysis, but the low complexity (AC:L) means a working DDL/query pair is trivial to construct. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Aug 26, 2026
Server-side request forgery in Apache Hive versions 2.1.0 through 4.2.0 lets an authenticated user with CREATE TABLE rights coerce the HiveServer2/Metastore process into fetching an attacker-chosen URL by planting a crafted avro.schema.url table property on an Avro table that is later queried. The fetch runs with the Hive service identity, exposing cloud instance metadata (e.g. 169.254.169.254), internal-only network services, and local files. No public exploit is identified at time of analysis and EPSS is low (0.29%), but the CVSS 9.1 rating and low attack complexity make it a meaningful post-authentication risk; upgrade to 4.2.1 resolves it.
Earlier versions of this analysis (1)
Server-Side Request Forgery in Apache Hive's Avro SerDe schema resolution allows an authenticated remote attacker holding CREATE TABLE privilege to make the Hive server issue outbound HTTP, HTTPS, or file:// requests to an arbitrary attacker-controlled URL by setting the avro.schema.url table property on an Avro-format table. All Apache Hive releases before 4.2.1 are affected; the vendor-confirmed fix is version 4.2.1, documented in advisory https://lists.apache.org/thread/6d56mk501fp4f8cb5wvrpj2jwd9knt05. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the SSRF primitive is critically impactful in cloud-hosted deployments where the Hive server process can reach instance metadata services, internal APIs, or local files.
RemediationAI
Vendor-released patch: upgrade to Apache Hive 4.2.1, which allowlists permitted avro.schema.url schemes and disables http/https/file fetches by default (per commit 45049202 and the Apache advisory thread https://lists.apache.org/thread/6d56mk501fp4f8cb5wvrpj2jwd9knt05). If you cannot upgrade immediately, apply compensating controls: tighten authorization so untrusted users do not hold CREATE TABLE / ALTER TABLE privileges (removes the primary attack path but restricts legitimate self-service table creation); at the network layer, block the Hive host's egress to link-local metadata endpoints (169.254.169.254) and to internal services it does not need, and enforce IMDSv2 / hop-limit on cloud metadata to blunt credential theft (side effect: may break tooling that relies on IMDSv1); and use the detection guidance to audit existing Avro tables for avro.schema.url values using http/https/file/ftp schemes or internal/link-local targets and remediate them. Post-upgrade, if remote HTTP schema fetch is genuinely needed, enable it deliberately via hive.avro.schema.url.remote.http.enabled with an explicit hive.avro.schema.url.http.allowed.hosts list rather than leaving it open.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache Hive is a SQL query engine over Hadoop-compatible storage; the vulnerability lives in its Avro SerDe schema-resolution path. Avro-backed tables may declare a schema location via the avro.schema.url table property, and Hive resolves and fetches that URL when the table is read to obtain the Avro record schema. Because the code accepted arbitrary URI schemes (including http, https, file, ftp) without an allowlist, a user-controlled property value becomes a server-side fetch target - the classic CWE-918 (SSRF) root cause. The vendor fix (commit 45049202) introduces scheme allowlisting (hive.avro.schema.url.allowed.schemes defaulting to trusted DFS schemes like hdfs/s3/abfs/gs), keeps http/https/file off by default (hive.avro.schema.url.remote.http.enabled=false plus an explicit host allowlist), and adds authorization entities so schema-URL filesystem reads are access-checked. Affected CPE is cpe:2.3:a:apache_software_foundation:apache_hive.
Know when Apache Hive gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Requires an authenticated user with CREATE TABLE rights so PR:L not PR:N; SSRF is a read-only fetch exposing data, so C:H with I:N and A:N.
Primary rating from Vendor (apache).
CVSS VectorVendor: apache
Lifecycle Timeline
3DescriptionCVE.org
Server-Side Request Forgery (SSRF) in Avro SerDe schema resolution in Apache Hive before 4.2.1 allows an authenticated remote attacker with CREATE TABLE privilege to cause the Hive server to fetch an attacker-controlled URL when resolving the avro.schema.url table property on an Avro table that is subsequently queried. This can expose cloud instance metadata, internal network services, or local server files to the Hive process identity. Users are recommended to upgrade to version 4.2.1, which fixes this issue.
Attacker access requirements:
- Network access to HiveServer2 / Metastore: required (remote attacker model).
- Valid Hive authentication: required.
- CREATE TABLE (or equivalent) privilege: required, so the attacker can set avro.schema.url in table properties.
- SELECT privilege on the malicious table: not required for the creator, who can typically query their own table; any other user granted SELECT can also trigger the fetch.
- Write access to the table LOCATION: not required; the attack uses the schema URL, not the data path.
- Admin / superuser privileges: not required; an ordinary authenticated user with DDL rights is sufficient.
- External tables enabled: typically required in practice, and enabled by default in most deployments.
Detection guidance:
- Inspect metastore / Hive table metadata for Avro tables whose avro.schema.url uses unexpected schemes such as http, https, file, or ftp, or points at link-local / cloud metadata addresses (for example 169.254.169.254) or other internal hosts.
- Review HiveServer2 and Metastore logs around CREATE/ALTER TABLE and queries against Avro tables for schema-resolution failures or outbound fetches of avro.schema.url.
- Correlate CREATE TABLE / ALTER TABLE activity that sets avro.schema.url with subsequent SELECT activity on the same table, especially when the URL target is unusual for schema distribution.
- On cloud deployments, check instance / VPC flow logs and metadata service access logs for unexpected requests from Hive host identities shortly after Avro DDL or query activity.
Articles & Coverage 1
Executive ViewAI
Apache Hive versions 2.1.0 through 4.2.0 contain a server-side request forgery vulnerability allowing authenticated users with table creation rights to retrieve sensitive data including cloud credentials and metadata. No public exploits currently exist, but organizations face significant exposure of infrastructure credentials and internal network information if database users become compromised or act maliciously.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
More in Apache Hive
View allSQL injection in the Apache Hive Metastore (versions 4.0.0 through 4.2.0) lets a caller who can invoke partition-name Me
Authentication bypass in Apache HiveServer2 4.0.0-4.2.0 allows unauthenticated network attackers to impersonate any Hive
EUVD-2026-65395
GHSA-gp8m-92x3-q87g
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB