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
6DescriptionCVE.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
AnalysisAI
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. …
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 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. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals are mixed and should be weighed together. … 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: 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). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all systems running Apache Hive versions 2.1.0 through 4.2.0 and inventory which users have CREATE TABLE permissions. …
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 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
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-65395
GHSA-gp8m-92x3-q87g