CVE-2026-56207

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Trending — 3 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: 0%CVSS: 9.8Exploit: None knownExposed: 0

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

Signature of Bearer token is not verified in last step of SAML2 authentication for Impala's hs2-http interface, allowing altering user name and acting as another user.

This issue affects Apache Impala: >=4.0.0.

Users are recommended to upgrade to version 4.5.2, which fixes this issue.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Sep 17, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-56207: Apache Impala: SAML authentication bypass via forged bearer token

http://www.openwall.com/lists/oss-security/2026/09/08/22

Vendor Advisories for CVE-2026-56207(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 55× in last 7d / 79× 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-09-19 19:55 UTCGHSA enrichment
  2. 2026-09-19 15:59 UTCEG score recompute
  3. 2026-09-19 15:58 UTCGHSA enrichment
  4. 2026-09-19 11:57 UTCGHSA enrichment
  5. 2026-09-19 08:02 UTCGHSA enrichment
  6. 2026-09-19 04:05 UTCGHSA enrichment
  7. 2026-09-19 00:09 UTCGHSA enrichment
  8. 2026-09-18 20:13 UTCEG score recompute
  9. 2026-09-18 20:13 UTCGHSA enrichment
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 16:13 UTCGHSA enrichment
  12. 2026-09-18 11:58 UTCGHSA enrichment
  13. 2026-09-18 08:02 UTCGHSA enrichment
  14. 2026-09-18 04:06 UTCGHSA enrichment
  15. 2026-09-18 00:11 UTCGHSA enrichment
  16. 2026-09-17 20:15 UTCEG score recompute
  17. 2026-09-17 20:15 UTCGHSA enrichment
  18. 2026-09-17 19:31 UTCEPSS rescore
  19. 2026-09-17 14:41 UTCGHSA enrichment
  20. 2026-09-17 10:44 UTCGHSA enrichment
  21. 2026-09-17 06:47 UTCGHSA enrichment
  22. 2026-09-17 02:51 UTCGHSA enrichment
  23. 2026-09-16 22:54 UTCGHSA enrichment
  24. 2026-09-16 18:58 UTCGHSA enrichment
  25. 2026-09-16 15:02 UTCEG score recompute
Show 54 more
  1. 2026-09-16 15:02 UTCGHSA enrichment
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-16 11:06 UTCGHSA enrichment
  4. 2026-09-16 07:10 UTCEG score recompute
  5. 2026-09-16 07:10 UTCGHSA enrichment
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-16 03:14 UTCGHSA enrichment
  8. 2026-09-15 23:18 UTCGHSA enrichment
  9. 2026-09-15 19:08 UTCGHSA enrichment
  10. 2026-09-15 15:13 UTCGHSA enrichment
  11. 2026-09-15 11:17 UTCGHSA enrichment
  12. 2026-09-15 07:21 UTCGHSA enrichment
  13. 2026-09-15 03:25 UTCEG score recompute
  14. 2026-09-15 03:25 UTCGHSA enrichment
  15. 2026-09-15 03:11 UTCEPSS rescore
  16. 2026-09-14 23:29 UTCGHSA enrichment
  17. 2026-09-14 19:09 UTCGHSA enrichment
  18. 2026-09-14 15:13 UTCGHSA enrichment
  19. 2026-09-14 11:17 UTCGHSA enrichment
  20. 2026-09-14 07:21 UTCGHSA enrichment
  21. 2026-09-14 03:25 UTCGHSA enrichment
  22. 2026-09-13 23:29 UTCGHSA enrichment
  23. 2026-09-13 19:34 UTCEG score recompute
  24. 2026-09-13 19:34 UTCGHSA enrichment
  25. 2026-09-13 16:47 UTCEPSS rescore
  26. 2026-09-13 15:37 UTCGHSA enrichment
  27. 2026-09-13 11:39 UTCGHSA enrichment
  28. 2026-09-13 07:43 UTCGHSA enrichment
  29. 2026-09-13 03:48 UTCGHSA enrichment
  30. 2026-09-12 23:52 UTCGHSA enrichment
  31. 2026-09-12 19:56 UTCGHSA enrichment
  32. 2026-09-12 16:00 UTCEG score recompute
  33. 2026-09-12 16:00 UTCGHSA enrichment
  34. 2026-09-12 12:04 UTCGHSA enrichment
  35. 2026-09-12 08:08 UTCGHSA enrichment
  36. 2026-09-12 04:12 UTCGHSA enrichment
  37. 2026-09-12 00:15 UTCGHSA enrichment
  38. 2026-09-11 20:19 UTCGHSA enrichment
  39. 2026-09-11 16:23 UTCEG score recompute
  40. 2026-09-11 16:23 UTCGHSA enrichment
  41. 2026-09-11 14:53 UTCEPSS rescore
  42. 2026-09-11 12:26 UTCEG score recompute
  43. 2026-09-11 12:26 UTCGHSA enrichment
  44. 2026-09-11 08:26 UTCGHSA enrichment
  45. 2026-09-11 04:30 UTCGHSA enrichment
  46. 2026-09-11 00:34 UTCGHSA enrichment
  47. 2026-09-10 20:38 UTCGHSA enrichment
  48. 2026-09-10 18:22 UTCEG score recompute 9.80
  49. 2026-09-10 18:22 UTCGHSA enrichment
  50. 2026-09-10 18:21 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  51. 2026-09-09 15:48 UTCGHSA enrichment
  52. 2026-09-09 11:24 UTCNVD update
  53. 2026-09-09 10:45 UTCEG score recompute
  54. 2026-09-09 10:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56207?
CVE-2026-56207 is a critical vulnerability published on September 9, 2026. Signature of Bearer token is not verified in last step of SAML2 authentication for Impala's hs2-http interface, allowing altering user name and acting as another user. This issue affects Apache Impala: >=4.0.0. Users are recommended to upgrade to version 4.5.2, which fixes this issue.
When was CVE-2026-56207 disclosed?
CVE-2026-56207 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56207 actively exploited?
CVE-2026-56207 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.3% of all scored CVEs.
What is the CVSS score of CVE-2026-56207?
CVE-2026-56207 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-56207?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56207, 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-56207

Explore →

Is Your Infrastructure Affected by CVE-2026-56207?

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