Quick answers
- Is CVE-2026-90466 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90466 being exploited in the wild.
- How severe is CVE-2026-90466?
- Informational severity, published 7 October 2026.
- Which products and versions are affected?
- Apache Impala 4.5.2.
- Is there a fix for CVE-2026-90466?
- Yes: fixed in 4.5.3. Until then: Ensure 'trusted_jar_paths' is either left empty or restricted to trusted administrators, and validate file upload permissions to prevent placement of attacker-controlled JARs in accessible filesystem locations. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-90466 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-90466?
- Check whether you run Apache Impala at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.5.3
Ensure 'trusted_jar_paths' is either left empty or restricted to trusted administrators, and validate file upload permissions to prevent placement of attacker-controlled JARs in accessible filesystem locations.
Technical details
The vulnerability allows path traversal in the 'trusted_jar_paths' startup flag, enabling an attacker to load a JAR file from a different filesystem location than intended by using relative paths that match a trusted path prefix. The attacker must first upload a malicious JAR to the target filesystem via Impala DDL operations (CREATE DATA SOURCE, CREATE TABLE), then use path traversal to reference it. Path traversal cannot override the URI schema, so the JAR must be on the same filesystem as the trusted path.
Affected products
- Apache Impala 4.5.2