CVE-2026-55976

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 28, 2026

Advisory Details (4)

Auto-updated Aug 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

[HIVE-29671] Fix SSRF in Avro SerDe via avro.schema.url and add schema-path authorization - ASF Jira

https://issues.apache.org/jira/browse/HIVE-29671
github_commit

commit 45049202df35 (apache/hive)

Fix landed in apache/hive commit 45049202df35 — awaiting tagged release

https://github.com/apache/hive/commit/45049202df35cea382616624de3fe8d252aa2d00
generic

GitHub - apache/hive: Apache Hive · GitHub

https://github.com/apache/hive

Vendor Advisories for CVE-2026-55976(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 36× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 05:39 UTCGHSA enrichment
  2. 2026-08-30 01:37 UTCEG score recompute
  3. 2026-08-30 01:37 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-29 21:34 UTCGHSA enrichment
  6. 2026-08-29 17:32 UTCGHSA enrichment
  7. 2026-08-29 12:32 UTCGHSA enrichment
  8. 2026-08-29 08:28 UTCGHSA enrichment
  9. 2026-08-29 04:24 UTCGHSA enrichment
  10. 2026-08-29 00:17 UTCEG score recompute
  11. 2026-08-29 00:17 UTCGHSA enrichment
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-28 17:42 UTCGHSA enrichment
  14. 2026-08-28 14:28 UTCGHSA enrichment
  15. 2026-08-28 10:25 UTCGHSA enrichment
  16. 2026-08-28 06:20 UTCGHSA enrichment
  17. 2026-08-28 02:15 UTCGHSA enrichment
  18. 2026-08-27 22:13 UTCGHSA enrichment
  19. 2026-08-27 18:11 UTCEG score recompute
  20. 2026-08-27 18:11 UTCGHSA enrichment
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-27 12:51 UTCGHSA enrichment
  23. 2026-08-27 08:48 UTCGHSA enrichment
  24. 2026-08-27 04:46 UTCGHSA enrichment
  25. 2026-08-27 00:44 UTCEG score recompute
Show 11 more
  1. 2026-08-27 00:44 UTCGHSA enrichment
  2. 2026-08-26 20:41 UTCGHSA enrichment
  3. 2026-08-26 19:27 UTCEG score recompute 9.10
  4. 2026-08-26 19:27 UTCGHSA enrichment
  5. 2026-08-26 19:26 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  6. 2026-08-26 16:59 UTCEG score recompute
  7. 2026-08-26 16:59 UTCGHSA enrichment
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 11:23 UTCNVD update
  10. 2026-08-25 10:22 UTCEG score recompute
  11. 2026-08-25 10:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55976?
CVE-2026-55976 is a critical vulnerability published on August 25, 2026. 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…
When was CVE-2026-55976 disclosed?
CVE-2026-55976 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55976 actively exploited?
CVE-2026-55976 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.5% of all scored CVEs.
What is the CVSS score of CVE-2026-55976?
CVE-2026-55976 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-55976?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55976, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55976

Explore →

Is Your Infrastructure Affected by CVE-2026-55976?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.