Skip to content
VulniPulse
Advisory severityMedium6.5Apache Software Foundation Updated

Medium [CVE-2026-90466] 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 medium-severity Apache Software Foundation advisory covers CVE-2026-90466; related products: Apache Impala.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-90466 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

Affected versions
  • Apache Impala 4.5.2 before 4.5.3

Official advisory · high-confidence parse· fetched 18 hours ago·verify at source

Fixed versions
  • 4.5.3

Official advisory · high-confidence parse· fetched 18 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Users are recommended to upgrade to version 4.5.3, which fixes this issue.

Official advisory · high-confidence parse· fetched 18 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.