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.
Security readout for executives and security teams
Plain-English summary
An authenticated Hive user with table-creation rights can make a vulnerable server retrieve a chosen schema URL when an Avro table is queried. The request could reach cloud metadata, internal services, or local files using the Hive process’s access. This creates serious confidentiality and integrity risk without requiring administrator privileges.
Executive priority
Treat internet-accessible, cloud-hosted, or multi-tenant Hive deployments as urgent. Upgrade promptly and investigate suspicious Avro table metadata and outbound access. Environments where only tightly trusted administrators hold DDL privileges have reduced likelihood, but the potential impact remains substantial.
Technical view
Apache Hive before 4.2.1 insufficiently validates the avro.schema.url table property during Avro SerDe schema resolution. A remote authenticated user with CREATE TABLE or equivalent rights can configure a URL that Hive fetches when the table is queried. The issue is classified as CWE-918 SSRF and is fixed in 4.2.1.
Likely exposure
Highest exposure exists where Hive before 4.2.1 permits less-trusted users to create Avro tables and Hive hosts can reach metadata endpoints, internal networks, or sensitive local files. External tables are typically required in practice and are commonly enabled. The source bundle’s affected-version entry conflicts with its broader description, so confirm exact applicability through Apache guidance.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as KEV. Exploitation requires network access, valid Hive authentication, and CREATE TABLE or equivalent privileges. A query against the crafted Avro table triggers retrieval; administrator privileges and write access to the table location are not required.
Researcher notes
The bundle reports CVSS 9.1 with PR:N, while its narrative requires authentication and CREATE TABLE privilege. It also lists only version 2.1.0 in structured affected data but describes all versions before 4.2.1 as vulnerable. These inconsistencies warrant checking the Apache advisory and commit when determining exact scoring and affected releases.
Mitigation direction
Upgrade Apache Hive to version 4.2.1 or later.
Restrict CREATE TABLE and equivalent DDL privileges to trusted users.
Limit Hive host access to cloud metadata endpoints and unnecessary internal services.
Review Apache guidance before applying compensating controls where immediate upgrading is impossible.
Validation and detection
Confirm every Hive deployment and package version, including hive-serde dependencies.
Inventory Avro tables with avro.schema.url properties and flag unexpected schemes or destinations.
Correlate CREATE or ALTER activity with later queries against the same Avro tables.
Review Hive, VPC flow, and metadata-service logs for unusual outbound requests.
Verify post-upgrade behavior using approved defensive tests in an isolated environment.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery
Server-Side Request Forgery represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.