ZeroHour
DashboardNewsCVEsExploitsIncidentsAIBriefAnalyticsEntitiesWatchlistIOCsAsk the feedSourcesFeeds & APIKiosk mode
Vendor

Arenadata

0 mentions in 7 days · 1 in 30 days · 1 total · first seen · last

Search everything

Timeline

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

Apache Impala CVE-2026-56207 allows forged SAML bearer tokens on the hs2-http interface, letting attackers impersonate other users; fixed in 4.5.2.

Apache Impala versions 4.0.0 through 4.5.1 fail to verify the bearer token signature in the final step of SAML2 authentication for the hs2-http interface. An attacker can alter the username and act as another user. Users are recommended to upgrade to version 4.5.2, and Apache rated the issue critical. It was reported by Andrew Rukin of Arenadata.

oss-security · 7d agoVulnerability 3 sourcesCVE-2026-562071

Related CVEs

  • CVE-2026-562079.8<1%
    SAML2 authentication bypass in Apache Impala hs2-http via unverified bearer token
    Apache Impala's final step of SAML2 authentication on its hs2-http interface accepts a Bearer token without verifying its cryptographic signature (CWE-347). An attacker with network access to the hs2-http endpoint can submit a forged bearer token with an altered user name, and Impala will accept it as valid. This lets the attacker impersonate another user and act as that user within Impala, bypassing the SAML2 authentication control. All Apache Impala releases from version 4.0.0 onward are affected when SAML2 authentication is used with the hs2-http interface; the issue is fixed in version 4.5.2. No public proof-of-concept or in-the-wild exploitation is known, the flaw is not in CISA KEV, and CVSS has not yet been assigned.
    · Apache Impala >= 4.0.0 (fixed in 4.5.2)niche

Appears with

product Apache Impala 1vendor Apache 1
Entities are extracted by the model from each article. Watching an entity keeps it in this browser only (no account); the watchlist page and dashboard alerts use it.