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.
- Bearer token signature is not verified in the SAML2 authentication flow
- Affects Impala 4.0.0 through 4.5.1 on the hs2-http interface
- Allows impersonation of arbitrary users by altering the username
- Fixed in Apache Impala 4.5.2
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-56207 | 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. Do: Upgrade to Apache Impala 4.5.2 as soon as practical. Until patched, restrict network access to the hs2-http interface and review hs2-http authentication/audit logs for sessions whose user name does not match corresponding IdP sign-in records to detect possible impersonation. Check whether your deployment actually uses SAML2 authentication on hs2-http, since other configurations are not affected, and watch the Apache advisory for CVSS scoring. | 9.8 | <1% |
| nichelikely low thousands of clusters at most; only Impala >= 4.0.0 deployments with SAML2 authentication enabled on the hs2-http interface |
Posted by Michael Smith on Sep 08 Severity: critical Affected versions: - Apache Impala 4.0.0 through 4.5.1 Description: 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. Credit: Andrew Rukin (Arenadata) (reporter) References:...
This source does not provide full text. Read it at seclists.org.