EUVD-2026-104145
GHSA-87c4-jmq5-gw73
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Kylin table metadata API
-
DeliverySubmit crafted tables/names input
-
ExploitBreak out of SparkSQL context
-
ExecutionExecute injected query
-
ImpactRead unauthorized data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires reaching Apache Kylin's table metadata API and supplying unsanitized 'tables'/'names' input that is passed into a SparkSQL command; the affected versions are 4.0.0 through 5.0.4. The vendor states impact is only moderate in query-only mode (the default, most common mode), which LIMITS realistic impact to data read/exposure rather than write or full compromise - a non-default (non-query-only) mode would likely raise impact. Because no CVSS vector is published, the exact authentication level needed is not confirmed, but the JIRA's 'authorization issue in table metadata API' framing indicates API access to that endpoint is a prerequisite. Upgrading to 5.0.5 removes the condition entirely. |
| Impact | This is a genuinely moderate, not critical, priority. The vulnerability is a SparkSQL injection (CWE-89 class) reachable through the table metadata API (per KYLIN-6109, framed as a 'Potential authorization issue in table metadata API'), but the ASF advisory explicitly caps impact as moderate when Kylin runs in query-only mode - which is described as the default and most common deployment mode - so realistic impact is largely data read/exposure rather than full write or takeover. No CVSS vector, EPSS score, KEV listing, or public POC is present in any provided source, so exploitation-probability and active-exploitation signals cannot be derived; the only severity signal is the vendor's qualitative 'moderate' rating. CRITICAL CAVEAT: because no CVSS vector is supplied, authentication requirements cannot be confirmed from the data - the JIRA 'authorization issue' framing suggests some level of API access is involved, but this is INFERRED, not confirmed. Overall, treat as a patch-in-normal-cycle item unless Kylin is exposed to untrusted users or beyond query-only mode, in which case prioritize higher; verify the exploitation preconditions with Apache before downgrading. |
| Exploit ScenarioDerived | An attacker with access to the Apache Kylin table metadata API supplies crafted table or name identifiers that are not properly neutralized before being incorporated into a SparkSQL statement, injecting attacker-controlled SQL. In the default query-only mode this most plausibly yields unauthorized reading of data or metadata the attacker should not reach; no public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
SQL injection in Apache Kylin 4.0.0 through 5.0.4 lets an authenticated user who can reach the table metadata API pass unsanitized 'tables'/'names' input that is concatenated into a SparkSQL command, yielding limited data exposure and limited integrity impact (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). The vendor explicitly scopes real-world impact as moderate because the default and most common deployment is query-only mode, which constrains attackers largely to reading data rather than writing or taking over the cluster; non-default modes would likely increase impact. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the issue is resolved by upgrading to Apache Kylin 5.0.5.
RemediationAI
Vendor-released patch: Apache Kylin 5.0.5, which resolves KYLIN-6109; upgrading from any 4.0.0-5.0.4 release to 5.0.5 removes the vulnerable code path and is the recommended action (references: https://kylin.apache.org/ and https://issues.apache.org/jira/browse/KYLIN-6109). If the upgrade cannot be performed immediately, the most effective compensating control is to restrict access to the table metadata API and its 'tables'/'names' parameters - place the REST endpoint behind authentication and network ACLs so only trusted operators and BI integrations can reach it, since the defect requires an authenticated caller; the trade-off is that legitimate metadata tooling and UI features that call the endpoint will break until credentials or allow-lists are distributed. Keeping Kylin in its default query-only mode limits the achievable impact to data read and limited integrity effects, but it is a risk-reduction measure rather than a fix and will not suit environments that rely on write paths. Deploying a reverse proxy or WAF rule that rejects SQL metacharacters in the metadata API parameters can block trivial payloads, though such signature-based filtering is bypassable and may produce false positives on legitimate table names. Monitor Kylin audit logs for anomalous metadata API calls containing SQL syntax as a detection measure while remediation is pending.
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 Kylin is an OLAP engine that pre-computes multidimensional cubes and executes analytic SQL through a compute engine; current releases integrate Apache Gluten and execute SparkSQL internally. The flaw is the classic Improper Neutralization of Special Elements used in an SQL Command (CWE-89): values supplied to the table metadata API - specifically the 'tables' and 'names' parameters - are not validated or escaped before being embedded in a SparkSQL statement, so crafted input alters the structure of the query the engine executes. The Apache JIRA entry KYLIN-6109 frames the same defect as an authorization issue in the table metadata API, indicating that access to that endpoint (and therefore authentication) is a prerequisite, consistent with the PR:L in the assessed vector. Because the vulnerable path terminates in the SparkSQL layer rather than a generic database client, the injected command runs with the privileges of Kylin's own query service, which is why the vendor stresses that impact is moderate in the default query-only mode and higher only when Kylin is configured for non-query workloads. No CPE strings or formally mapped CWE identifier were published in the source data; the CWE-89 classification is taken from the advisory's own wording.
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
Network-reachable API (AV:N), no published vector so AC:L; the 'authorization issue' framing implies some authenticated API access (PR:L); query-only default limits impact to partial read/write (C:L/I:L/A:N).
Estimated by vuln.today — no official severity rating has been published for this CVE yet.
Description PRE-NVD
Threat Intelligence Overview
CVE.org
EPSS
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
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Exploit-DB