CVE-2026-90466: Apache Path traversal of 'trusted_jar_paths' in Impala 4.5.2 allows an attacker-controlled JAR to be loaded via a relative path where the prefix matches a path specified in 'trusted_jar_paths'
This Apache advisory covers CVE-2026-90466. Related products: Apache Impala.
- CVE-2026-90466
Key facts
- Vendor rating
- Medium, CVSS 6.5
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N· base score 6.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.- Weakness
- CWE-23 Relative path traversal
- EPSS
- 0.50% chance of exploitation in the next 30 days (43rd percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Versions named
- Apache Impala 4.5.2 before 4.5.3
- Fixed in
- 4.5.3
- Source published
- Source revised
- Listed by VulniPulse
- Record changed
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Related products & platforms
Description
Path traversal of 'trusted_jar_paths' in Impala 4.5.2 allows an attacker-controlled JAR to be loaded via a relative path where the prefix matches a path specified in 'trusted_jar_paths'.
The startup flag 'trusted_jar_paths' references URIs for loading files from local or remote filesystems. 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.
Path traversal can only be used if a trusted path exists, so this attack requires 'trusted_jar_paths' have a non-empty value configured by the Impala admin.
Users are recommended to upgrade to version 4.5.3, which fixes this issue.
Affected product named by the advisory: Apache Impala.
Text from the source record.
- Apache Impala 4.5.2 before 4.5.3
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-90466
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- Users are recommended to upgrade to version 4.5.3, which fixes this issue.
More Apache Software Foundation advisories
CVE-2026-97720Oct 7, 2026Incorrect implementation of JWT/OAuth authentication in Impala executors in Apache ImpalaCVE-2026-65181Sep 9, 2026Insufficient authorization of Data Source tables in Impala 2.7-4.5CVE-2026-56207Sep 9, 2026Apache Impala: Signature of Bearer token is not verified in last step of SAML2CVE-2026-96295Nov 20, 2026Apache Texera: Authenticated users can bypass normal controls on the reading and writingCVE-2026-121649Nov 19, 2026Apache Tomcat information disclosureCVE-2026-133325Nov 19, 2026Key exchange without entity authentication vulnerability in Apache Tomcat
Apache Software Foundation advisories, October 2026All Apache Software Foundation advisories
Get an email when Apache publishes the next one.
See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.