CVE-2026-49845

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
9.8EG
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.8Exploit: None knownExposed: 0

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

SQL injection in Hive Metastore direct SQL partition-name resolution in Apache Hive before 4.2.1 on all platforms allows authenticated users with access to Hive Metastore APIs to read, modify, or affect unintended partition metadata (including statistics updates, truncation targets, and file-metadata cache operations) via crafted partition names in metastore RPC requests when direct SQL is enabled (the default). Users are recommended to upgrade to version 4.2.1, which fixes this issue.

Details about the issue: Several Hive Metastore RPCs resolve partitions by full partition name (PART_NAME) through direct-SQL helpers. In those paths, client-supplied partition names are embedded into SQL using string concatenation (DirectSqlUpdatePart.quoteString() → '...') instead of bind parameters. A partition name containing a single quote (and crafted SQL) can alter the generated WHERE clause so that lookups intended for one partition match additional rows. That can affect reads, stats updates, truncate targets, metadata-cache targets, and related operations when metastore.try.direct.sql is enabled (default: true). An authenticated or network-trusted caller with the ability to invoke Hive Metastore partition-name APIs against a target table (directly or via Hive/other clients), when direct SQL is enabled can perform this attack. Also, the impact is mainly within table & partition targeting (read/update/truncate/drop/cache the wrong partitions in a table they can reference), not arbitrary cross-database access via this bug alone.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 27, 2026

Advisory Details (4)

Auto-updated Aug 27, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic
https://lists.apache.org/thread/6d56mk501fp4f8cb5wvrpj2jwd9knt05
generic

[HIVE-29622] Potential vulnerability in HiveMetaStore partition-name direct-SQL paths - ASF Jira

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

commit ca64f08a8e43 (apache/hive)

Fix landed in apache/hive commit ca64f08a8e43 — awaiting tagged release

https://github.com/apache/hive/commit/ca64f08a8e43db9845b47d5fa2e96f7fdea7288e
generic

GitHub - apache/hive: Apache Hive · GitHub

https://github.com/apache/hive

Vendor Advisories for CVE-2026-49845(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 40× in last 7d / 40× 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 02:28 UTCEG score recompute
  2. 2026-08-30 02:28 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 22:09 UTCGHSA enrichment
  5. 2026-08-29 17:49 UTCGHSA enrichment
  6. 2026-08-29 13:25 UTCGHSA enrichment
  7. 2026-08-29 08:59 UTCGHSA enrichment
  8. 2026-08-29 04:40 UTCGHSA enrichment
  9. 2026-08-29 00:17 UTCEG score recompute
  10. 2026-08-29 00:17 UTCGHSA enrichment
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-28 16:29 UTCGHSA enrichment
  13. 2026-08-28 12:06 UTCGHSA enrichment
  14. 2026-08-28 07:46 UTCGHSA enrichment
  15. 2026-08-28 03:25 UTCGHSA enrichment
  16. 2026-08-27 23:05 UTCGHSA enrichment
  17. 2026-08-27 18:45 UTCGHSA enrichment
  18. 2026-08-27 14:44 UTCEG score recompute
  19. 2026-08-27 14:44 UTCGHSA enrichment
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-27 10:25 UTCGHSA enrichment
  22. 2026-08-27 06:05 UTCGHSA enrichment
  23. 2026-08-27 01:39 UTCGHSA enrichment
  24. 2026-08-26 21:19 UTCGHSA enrichment
  25. 2026-08-26 16:59 UTCEG score recompute
Show 15 more
  1. 2026-08-26 16:59 UTCGHSA enrichment
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-26 12:50 UTCGHSA enrichment
  4. 2026-08-26 08:31 UTCGHSA enrichment
  5. 2026-08-26 04:11 UTCEG score recompute
  6. 2026-08-26 04:11 UTCGHSA enrichment
  7. 2026-08-26 00:44 UTCEG score recompute
  8. 2026-08-26 00:44 UTCGHSA enrichment
  9. 2026-08-25 20:24 UTCGHSA enrichment
  10. 2026-08-25 19:50 UTCEG score recompute▲ 9.80
  11. 2026-08-25 19:50 UTCGHSA enrichment
  12. 2026-08-25 19:49 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  13. 2026-08-25 11:23 UTCNVD update
  14. 2026-08-25 10:22 UTCEG score recompute
  15. 2026-08-25 10:21 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49845?
CVE-2026-49845 is a critical vulnerability published on August 25, 2026. SQL injection in Hive Metastore direct SQL partition-name resolution in Apache Hive before 4.2.1 on all platforms allows authenticated users with access to Hive Metastore APIs to read, modify, or affect unintended partition metadata (including statistics updates, truncation targets, and…
When was CVE-2026-49845 disclosed?
CVE-2026-49845 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49845 actively exploited?
CVE-2026-49845 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 58.2% of all scored CVEs.
What is the CVSS score of CVE-2026-49845?
CVE-2026-49845 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-49845?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49845, 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-49845

Explore →

Is Your Infrastructure Affected by CVE-2026-49845?

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

Start Free Scan →Browse All CVEs