Apache Impala security advisories
Security information for Apache Impala
Reporting
Do you want disclose a potential security issue for Apache Impala? Send your report to the Apache Security Team.
You can read more about the security policy on:
Advisories
This section is experimental: it provides advisories since 2023 and may lag behind the official CVE publications. It may also lack details found on the project security page linked above. If you have any feedback on how you would like this data to be provided, you are welcome to reach out on our public mailinglist or privately on security@apache.org
RCE via External Data Source Class Loading
CVE-2026-65181 [CVE] [CVE json] [OSV json]
Last updated: 2026-09-09T10:40:47.268Z
Affected
- Apache Impala from 2.7.0 through 4.5.1
Description
Insufficient authorization of Data Source tables in Impala 2.7-4.5 allows a client with privileges to upload a file to remote storage and create a table to execute arbitrary Java code.
Users are recommended to upgrade to version 4.5.2, which fixes this issue.
References
Credits
- zhaokaifei ChinaTelecom (reporter)
Secrets Exfiltration via SSRF
CVE-2026-57866 [CVE] [CVE json] [OSV json]
Last updated: 2026-09-09T10:39:32.832Z
Affected
- Apache Impala from 4.4.0 through 4.5.1
Description
Server side request forgery in Apache Impala versions 4.4.x and 4.5.x. Authenticated Impala users with permissions to execute the ai_generate_text() function can exfiltrate secrets provided by the credential providers configured in the <code>hadoop.security.credential.provider.path property of </code>core-site.xml. The secret’s key must be known to the user.
References
Credits
- Andrey Rukin (Arenadata) (reporter)
SAML authentication bypass via forged bearer token
CVE-2026-56207 [CVE] [CVE json] [OSV json]
Last updated: 2026-09-09T10:36:50.910Z
Affected
- Apache Impala from 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.
References
Credits
- Andrew Rukin (Arenadata) (reporter)
Avro Schema URL Server-Side Request Forgery
CVE-2026-54048 [CVE] [CVE json] [OSV json]
Last updated: 2026-09-09T10:33:43.525Z
Affected
- Apache Impala from 2.0.0 through 4.5.1
Description
Specifying tblproperties(‘avro.schema.url’=’http://…’) or with a ‘file:///’ URI on a table in Impala 2.0.0 to 4.5.1 on all platforms allows an attacker to trigger a GET request to internal endpoints they may not have access to but that Impala does and the response my be exposed via parsing error messages.
Users are recommended to upgrade to version 4.5.2, which fixes this issue.
References
Credits
- zhaokaifei ChinaTelecom (reporter)
Impala logs contain secrets
CVE-2021-28131 [CVE] [CVE json] [OSV json]
Last updated: 2021-07-22T09:44:57.855Z
Affected
- Apache Impala from Apache Impala through 3.4.0
Description
Impala sessions use a 16 byte secret to verify that the session is not being hijacked by another user. However, these secrets appear in the Impala logs, therefore Impala users with access to the logs can use another authenticated user’s sessions with specially constructed requests. This means the attacker is able to execute statements for which they don’t have the necessary privileges otherwise.
Impala deployments with Apache Sentry or Apache Ranger authorization enabled may be vulnerable to privilege escalation if an authenticated attacker is able to hijack a session or query from another authenticated user with privileges not assigned to the attacker.
Impala deployments with audit logging enabled may be vulnerable to incorrect audit logging as a user could undertake actions that were logged under the name of a different authenticated user.
Constructing an attack requires a high degree of technical sophistication and access to the Impala system as an authenticated user.
Mitigation: If an Impala deployment uses Apache Sentry, Apache Ranger or audit logging, then users should upgrade to a version of Impala with the fix for IMPALA-10600. The Impala 4.0 release includes this fix. This hides session secrets from the logs to eliminate the risk of any attack using this mechanism.
In lieu of an upgrade, restricting access to logs that expose secrets will reduce the risk of an attack. Restricting access to the Impala deployment to trusted users will also reduce the risk of an attack. Log redaction techniques can be used to redact secrets from the logs.