Unknown [CVE-2026-55976] Apache Hive: SSRF vulnerability in Hive Avro Serde due to Insufficient input validation on avro.schema.url
This security Apache Software Foundation advisory covers CVE-2026-55976 affecting Apache Hive.
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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:
- Apache Hive 2.1.0 through 4.2.0
Official advisory · medium-confidence parse· fetched 46 minutes ago·verify at source
- 4.2.1
Official advisory · medium-confidence parse· fetched 46 minutes ago·verify at source
Mitigation checklist
- Users are recommended to upgrade to version 4.2.1, which fixes this issue.
Official advisory · medium-confidence parse· fetched 46 minutes ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.