CVE-2026-55976

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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 (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.1Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation1.0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
63rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

September 28, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
Fix named in the CVE record. Sources: github_commit.
Web page

[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
Web page

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 24× in last 7d / 181× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 327 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 227 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 09:23 UTCEG score recompute
  2. 2026-10-14 09:23 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  4. 2026-10-13 06:49 UTCEG score recompute
  5. 2026-10-13 06:49 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  7. 2026-10-12 15:55 UTCEG score recompute
  8. 2026-10-12 06:52 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-11 19:38 UTCEG score recompute
  10. 2026-10-11 16:53 UTCEG score recompute
  11. 2026-10-11 14:16 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  14. 2026-10-10 16:22 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-10 12:18 UTCEG score recompute
  16. 2026-10-10 12:18 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  18. 2026-10-09 04:31 UTCEG score recompute
  19. 2026-10-09 04:31 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  21. 2026-10-08 07:37 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-08 03:34 UTCEG score recompute
  23. 2026-10-08 03:33 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  25. 2026-10-07 09:56 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
Show 75 more
  1. 2026-10-07 05:13 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  2. 2026-10-07 01:10 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-06 20:45 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-10-06 16:09 UTCEG score recompute
  5. 2026-10-06 16:09 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  7. 2026-10-06 11:58 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-06 07:43 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-06 02:38 UTCEG score recompute
  10. 2026-10-06 02:38 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  11. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  12. 2026-10-05 17:03 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-05 12:05 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-10-05 08:02 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-05 03:58 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-10-04 23:54 UTCEG score recompute
  17. 2026-10-04 23:54 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  19. 2026-10-04 19:51 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-10-04 14:40 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-04 10:20 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-04 06:18 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  23. 2026-10-04 02:15 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-03 20:29 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-03 16:27 UTCEG score recompute
  26. 2026-10-03 16:27 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  27. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  28. 2026-10-03 05:02 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  29. 2026-10-03 00:36 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  30. 2026-10-02 19:09 UTCEG score recompute
  31. 2026-10-02 19:08 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  32. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  33. 2026-10-02 15:06 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  34. 2026-10-02 11:03 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  35. 2026-10-02 06:29 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  36. 2026-10-02 01:18 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  37. 2026-10-01 20:15 UTCEG score recompute
  38. 2026-10-01 20:15 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  39. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  40. 2026-10-01 13:44 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  41. 2026-10-01 09:39 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  42. 2026-10-01 05:37 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  43. 2026-10-01 01:07 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  44. 2026-09-30 20:16 UTCEG score recompute
  45. 2026-09-30 20:16 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  46. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  47. 2026-09-30 11:43 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  48. 2026-09-30 06:51 UTCEG score recompute
  49. 2026-09-30 06:51 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  50. 2026-09-29 15:22 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  51. 2026-09-29 14:38 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  52. 2026-09-29 07:22 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  53. 2026-09-29 03:20 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  54. 2026-09-28 23:17 UTCEG score recompute
  55. 2026-09-28 23:17 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  56. 2026-09-28 21:30 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  57. 2026-09-28 16:26 UTCEG score recompute
  58. 2026-09-28 16:26 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  59. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  60. 2026-09-28 12:09 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  61. 2026-09-28 08:07 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  62. 2026-09-28 03:57 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  63. 2026-09-27 23:55 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  64. 2026-09-27 19:52 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  65. 2026-09-27 15:41 UTCEG score recompute
  66. 2026-09-27 15:41 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  67. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  68. 2026-09-27 10:58 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  69. 2026-09-27 06:49 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  70. 2026-09-27 02:18 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  71. 2026-09-26 22:08 UTCEG score recompute
  72. 2026-09-26 22:08 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  73. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  74. 2026-09-25 16:43 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1
  75. 2026-09-25 12:30 UTCGHSA enrichmentGHSA-gp8m-92x3-q87g · GitHub severity CRITICAL · GitHub CVSS 9.1

Frequently asked(5)

What is CVE-2026-55976?
CVE-2026-55976 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-55976 published?
The CVE record for CVE-2026-55976 was published on August 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 28, 2026; the record at its source may have been updated since.
Is CVE-2026-55976 actively exploited?
CVE-2026-55976 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-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?
The CVE record for CVE-2026-55976 names the fix: "Users are recommended to upgrade to version 4.2.1, which fixes this issue." The vendor advisories EchelonGraph has for CVE-2026-55976 are linked in the Vendor Advisories panel on this page.

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.