PatchSiren cyber security CVE debrief
CVE-2026-90466 Apache Software Foundation CVE debrief
Apache Impala 4.5.2 has a path traversal vulnerability allowing an attacker to load a JAR file outside of trusted paths if 'trusted_jar_paths' is configured. This vulnerability can be mitigated by upgrading to version 4.5.3. The 'trusted_jar_paths' configuration is used to reference URIs for loading files from local or remote filesystems. However, due to the path traversal vulnerability, an attacker-controlled JAR can be loaded via a relative path where the prefix matches a path specified in 'trusted_jar_paths'. Users should verify JAR file loading configurations and assess exposure of 'trusted_jar_paths' configuration.
- Vendor
- Apache Software Foundation
- Product
- Apache Impala
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-07
- Original CVE updated
- 2026-10-07
- Advisory published
- 2026-10-07
- Advisory updated
- 2026-10-07
Who should care
Apache Impala administrators and users who have 'trusted_jar_paths' configured are advised to verify JAR file loading configurations and assess exposure of 'trusted_jar_paths' configuration. They should prioritize upgrading to version 4.5.3 to fix the path traversal issue.
Why it matters
Apache Impala 4.5.2 path traversal vulnerability requires verification of JAR file loading configurations and upgrading to version 4.5.3 to fix the issue.
- Verify JAR file loading configurations
- Assess exposure of 'trusted_jar_paths' configuration
- Prioritize upgrading to version 4.5.3
Technical summary
Apache Impala 4.5.2 has a path traversal vulnerability in 'trusted_jar_paths' allowing an attacker to load a JAR file outside of trusted paths. The vulnerability can be used if a trusted path exists and 'trusted_jar_paths' have a non-empty value configured by the Impala admin. The path traversal can't override the schema but can result in loading a JAR that has been uploaded to a different location in that filesystem via Impala DDLs such as CREATE DATA SOURCE and CREATE TABLE. The issue is fixed in version 4.5.3, which users are recommended to upgrade to.
Defensive priority
Upgrade to version 4.5.3 to fix the path traversal issue in Apache Impala.
Recommended defensive actions
- Upgrade Apache Impala to version 4.5.3
- Review and validate 'trusted_jar_paths' configuration
- Monitor for potential JAR file loading issues
- Verify JAR file loading configurations
- Assess exposure of 'trusted_jar_paths' configuration
- Prioritize upgrading to version 4.5.3
- Review compensating controls for exposed systems
Evidence notes
The CVE record and source item provide details on the path traversal vulnerability in Apache Impala 4.5.2. The vulnerability allows an attacker to load a JAR file outside of trusted paths if 'trusted_jar_paths' is configured. Evidence of this vulnerability includes the CVE record and source item descriptions. Defenders should verify JAR file loading configurations and assess exposure of 'trusted_jar_paths' configuration to ensure the security of their systems.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-90466 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-90466
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-90466 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90466
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Apache Impala: Path traversal executes JARs outside trusted paths
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/90xxx/CVE-2026-90466.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://lists.apache.org/thread.html/m7qbho4j1g4v7kx7pbk4z2n8p9nx6bqn
Supplemental source - vendor-advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.