{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-90466 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-90466 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-90466 is a medium-severity path traversal vulnerability in Apache Impala, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90466 and fix it if it is affected.\n\nWhat it is: CVE-2026-90466 is a medium-severity path traversal vulnerability in Apache Impala, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90466 in the wild and no public exploit code.\n\nAffected product: Apache Impala. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90466/ (Markdown: https://insights.sbomify.com/CVE-2026-90466/index.md)","id":"CVE-2026-90466","markdown":"https://insights.sbomify.com/CVE-2026-90466/index.md","name":"CVE-2026-90466","record":{"aliases":["GHSA-xf54-j4ff-f2xp"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Impala","requires_auth":"low_privilege","summary":"Path traversal in Apache Impala allows loading malicious JARs from outside trusted paths, enabling code execution if trusted_jar_paths is configured.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"impala","vendor":"apache"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-23","name":"Relative Path Traversal"}],"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'.\n\nThe 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.\n\nUsers are recommended to upgrade to version 4.5.3, which fixes this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache Impala: Path traversal executes JARs outside trusted paths","id":"CVE-2026-90466","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"aiosmtplib before 5.1.3 ESMTP Parameter Injection via unvalidated addresses","id":"CVE-2026-90467"},"packages":[],"prev":{"headline":"Fireware OS Missing Authentication in FireCluster Sync Allows Privilege Escalation","id":"CVE-2026-90465"},"products":["Apache Impala"],"published":"2026-10-07","related":[{"cvss_score":9.8,"headline":"Apache Impala: SAML authentication bypass via forged bearer token","id":"CVE-2026-56207","kev_date_added":null,"published":"2026-09-09"},{"cvss_score":9.8,"headline":"Privilege escalation in Apache Impala","id":"CVE-2018-11792","kev_date_added":null,"published":"2018-10-24"},{"cvss_score":9.8,"headline":"Auth bypass in Apache Impala","id":"CVE-2017-5640","kev_date_added":null,"published":"2017-07-10"},{"cvss_score":8.8,"headline":"Apache Impala: Secrets Exfiltration via SSRF","id":"CVE-2026-57866","kev_date_added":null,"published":"2026-09-09"},{"cvss_score":8.1,"headline":"Apache Impala: RCE via External Data Source Class Loading","id":"CVE-2026-65181","kev_date_added":null,"published":"2026-09-09"},{"cvss_score":7.5,"headline":"Impala logs contain secrets","id":"CVE-2021-28131","kev_date_added":null,"published":"2021-07-22"},{"cvss_score":7.5,"headline":"Missing authorization in Impala","id":"CVE-2019-10084","kev_date_added":null,"published":"2019-11-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["Apache Software Foundation"]},"summary":"Path traversal in Apache Impala allows loading malicious JARs from outside trusted paths, enabling code execution if trusted_jar_paths is configured.","url":"https://insights.sbomify.com/CVE-2026-90466/"}