CVE-2026-55976: Apache Hive: SSRF vulnerability in Hive Avro Serde due to Insufficient input validation on avro.schema.url
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Hiveto a version that resolves this vulnerability.Fixed in 4.2.1 - Compensating control
Detect and respond to SSRF attempts by correlating CREATE TABLE/ALTER TABLE activity that sets the table property avro.schema.url with subsequent SELECT activity on the same Avro table, especially when the URL target is unusual for schema distribution.
- Compensating control
Inspect metastore/Hive table metadata for Avro tables whose avro.schema.url uses unexpected schemes such as http, https, file, or ftp, or that point to link-local/cloud metadata addresses (for example 169.254.169.254) or other internal hosts.
- Compensating control
On cloud deployments, review instance/VPC flow logs and metadata service access logs for unexpected requests from Hive host identities shortly after Avro DDL or query activity.
- Compensating control
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.
Event History
Frequently Asked Questions
Which users can exploit this issue?
An attacker needs network access to HiveServer2 or the Metastore, valid Hive authentication, and CREATE TABLE or equivalent DDL privileges. Administrator privileges and write access to the table LOCATION are not required.
What action triggers the server-side request?
The attacker creates an Avro table with an attacker-controlled avro.schema.url property, then the table is queried. The table creator can typically trigger the query themselves; another user with SELECT access to that table can also trigger the fetch.
What could the Hive server access if exploited?
The Hive process may fetch the attacker-controlled URL, potentially exposing cloud instance metadata, internal network services, or local server files accessible to the Hive process identity.
What is the available remediation?
Upgrade Apache Hive to version 4.2.1, which fixes the issue. The affected versions are Apache Hive releases before 4.2.1.