GHSA-gr7f-9f5r-v3mg
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-priv SQL user
-
DeliveryInject JavaScript into table alias
-
ExploitStore malicious query plan
-
ExecutionVictim opens plan in Web UI
-
ImpactScript executes in victim browser session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires (1) an authenticated Impala SQL account with at least SELECT permission to craft a table alias containing a JavaScript payload, and (2) a second, typically higher-privileged user to open that specific query plan in Impala's Web UI, where the stored payload executes - making victim interaction a hard prerequisite. Limiting factors: the Impala Web UI must be enabled and reachable by the victim; the attacker must already possess valid Impala credentials (not pre-auth); and impact is confined to the victim's browser security context rather than the Impala backend. These conditions make the flaw most relevant in multi-tenant Impala clusters where untrusted or lower-trust users share the environment with administrators. |
| Impact | This is a moderate-severity stored XSS (CWE-79) in Apache Impala's Web UI query-plan rendering, confirmed by the Apache vendor advisory and oss-security posting. No CVSS vector, EPSS score, KEV listing, or public POC is provided in the input, so quantitative exploitation-probability signals are entirely absent - this assessment is grounded in the description and vendor severity rating only. The vendor's own rating is 'moderate,' consistent with a stored XSS that requires an attacker to already hold a valid authenticated Impala SQL account (described as needing only SELECT permission) and that further depends on a separate victim user opening the malicious query plan in the Web UI. These two preconditions (low-privilege authenticated insider + victim interaction) substantially limit real-world risk versus a pre-auth network RCE, despite the network-reachable Web UI. There is no evidence of active exploitation ('no public exploit identified at time of analysis'), and the absence of EPSS/KEV data should NOT be read as low risk - it simply means those feeds were not supplied. Net: a credible insider/second-order-compromise issue worth patching in multi-tenant Impala deployments, but not an emergency mass-exploitation threat on current evidence. Note the input provides NO official CVSS vector, so all attack-vector/privilege claims below are the analyst's own assessment, not NVD-confirmed. |
| Exploit ScenarioDerived | A low-privileged analyst who holds only SELECT rights on a table runs or saves a query that embeds a JavaScript payload inside a table alias. When a higher-privileged operator or administrator later opens that query's plan in Impala's Web UI, the stored script executes in the admin's authenticated browser session, enabling session-context actions such as cookie/token theft or UI actions on the victim's behalf. No public proof-of-concept exploit is identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Stored cross-site scripting (CWE-79) in the Apache Impala Web UI query-plan view allows an authenticated SQL user holding only SELECT permission to embed JavaScript in a table alias, which then executes in the browser of any other user who opens that query plan. All Impala releases from 2.7.0 through 4.5.2 are affected; the vendor-released fix is version 4.5.3. Exploitation requires a valid Impala account plus a second user opening the crafted plan (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), and no public exploit identified at time of analysis. Risk is concentrated in multi-tenant clusters where low-trust analysts share an environment with administrators, since the injected script runs in the victim's browser origin rather than against the Impala backend.
RemediationAI
Upgrade to Apache Impala 4.5.3, the version named in the vendor advisory as the fix for CVE-2026-93684 (see https://impala.apache.org/ and the oss-security advisory at https://seclists.org/oss-sec/2026/q4/80). Until every worker and coordinator in the cluster is on 4.5.3 - mixed-version clusters should be treated as still vulnerable - reduce exposure by removing unnecessary network reachability to the Impala Web UI: it should never be exposed to general user networks or the internet, and firewall rules, VPN-only access, or a reverse proxy with authentication should restrict it to the small set of operators who genuinely need it, with the trade-off that administrators lose convenient plan debugging for any user not on the allowed path. If the Web UI is not required, disable it entirely at the daemon level (for example via the Impala web server enable/disable startup flags) - this eliminates the attack surface but also removes the monitoring, query-plan, and metrics dashboards that many operators rely on for troubleshooting. In environments where the UI must stay available, tighten the SQL privilege model so that only trusted accounts can create or run queries whose plans are broadly visible, and audit existing stored query plans and table aliases for injected markup before restoring normal plan sharing. There is no vendor-released patch other than 4.5.3 in the available data, and no input-sanitization workaround is documented, so version upgrade remains the only complete fix; sanitizing or truncating untrusted table aliases at the application layer, if feasible in your query pipelines, provides only partial mitigation and does not address plans already persisted.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache Impala is the Apache Software Foundation's open-source, native MPP analytic database for the Hadoop ecosystem, querying Iceberg and other open table formats and sharing Hive metastore metadata; it authenticates via Kerberos and authorizes via Apache Ranger, serving results both through ODBC/JDBC clients and through a built-in Web UI that renders query plans for operators and administrators. The defect is a stored/reflected cross-site scripting condition (CWE-79, improper neutralization of input during web page generation) in the component that renders SQL query plans: a table alias supplied by the query author is persisted with the plan and emitted into the Web UI's HTML without adequate output encoding, so script content in the alias survives as markup and is interpreted when a different user views that plan. Because the payload is stored in the plan rather than reflected immediately, the trigger is decoupled from the injection, and the CVSS scope metric is Changed (S:C) - code executes in the victim's browser security context, which is distinct from the Impala server process, so server-side data confidentiality and integrity are not directly at risk (C:L/I:L/A:N). The vector also confirms PR:L and UI:R, meaning the attacker must already be an authenticated Impala user and the victim must actively open the tainted query plan; the Web UI must additionally be enabled and reachable by the victim for the attack to land.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Web UI is network-reachable (AV:N) and attacker needs a low-priv authenticated SQL account (PR:L); a separate victim must open the plan (UI:R); stored XSS crosses into the victim's browser context (S:C) with limited C/I impact and no availability effect.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
2Description PRE-NVD
Executive ViewAI
Apache Impala's Web UI query-plan view is affected by a stored cross-site scripting vulnerability that allows any authenticated user with basic query permissions to inject JavaScript that executes in the browsers of other users, including administrators, on multi-tenant clusters. This can lead to session hijacking, unauthorized administrative actions, or data exposure, particularly where low-trust analysts share an environment with privileged users. Leadership should prioritize remediation because a single crafted query plan can compromise high-value administrative sessions and erode trust in the analytics platform.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-94224
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB