EUVD-2026-103150
GHSA-5wf3-g47p-2g8r
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed Kylin JobController endpoint
-
DeliveryReference another project's job IDs
-
ExploitBypass missing cross-project authorization check
-
ExecutionPause, cancel, or tamper target jobs
-
ImpactDisrupt or corrupt analytics pipelines
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The affected component is Apache Kylin's JobController, which fails to enforce project-scoped authorization, letting an actor manipulate jobs belonging to projects other than their own. Per the vendor advisory, meaningful exploitation requires the Kylin service to be directly reachable on the public network - explicitly noted as uncommon - and in-house (network-isolated) deployments are largely unaffected, which is the primary limiting factor. The 'cross-project' framing implies the actor must interact with Kylin's job-management API, and most likely hold a valid account in at least one project (inferred from the description, not confirmed by a CVSS vector). Applies to Apache Kylin versions 4.0.0 through 5.0.4; upgrading to 5.0.5 removes the condition. |
| Impact | This is an authorization/access-control flaw (missing cross-project isolation in Apache Kylin's JobController) rated 'important' by the vendor, but no CVSS vector, EPSS score, KEV listing, or public POC is present in the provided data, so most quantitative exploitation signals are MISSING and cannot be compared. Exploitation status per the available data is 'no public exploit identified at time of analysis.' The vendor explicitly scopes real-world risk downward: impact is greatest only for Kylin services directly exposed to the public network - which the advisory states is uncommon - and typical in-house deployments are mostly not impacted. Because no CVSS vector was supplied, authentication requirements are not confirmed from available data; the term 'cross-project' strongly implies an actor already authorized within at least one project, but this is INFERRED from the description, not confirmed by a PR metric. Net assessment: a genuine multi-tenant authorization weakness worth patching, but absent KEV/POC/EPSS and given the vendor's narrow exposure scoping, this is a moderate, deployment-dependent priority rather than a mass-exploitation emergency. |
| Exploit ScenarioDerived | An actor with network reach to an exposed Kylin instance (and, as implied by 'cross-project,' likely a valid account scoped to one project) sends requests to JobController endpoints referencing jobs belonging to a different project. Because the controller does not enforce per-project authorization, the actor can enumerate, pause, resume, cancel, or otherwise manipulate another project's build/query jobs. No public exploit code is 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
Unauthorized cross-project job manipulation in Apache Kylin 4.0.0 through 5.0.4 allows an authenticated user with a valid account in one project to operate on job records belonging to projects they are not a member of, because the JobController component does not enforce project-scoped authorization (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L). The vendor rates the issue 'important' but explicitly scopes real-world impact to Kylin services directly reachable from the public network, which it describes as uncommon; in-house, network-isolated deployments are largely unaffected. No publicly available exploit code and no CISA KEV listing were identified at time of analysis, and no EPSS score was available; upgrading to Apache Kylin 5.0.5 removes the condition.
RemediationAI
Vendor-released patch: Apache Kylin 5.0.5 - upgrading from any 4.0.0-5.0.4 deployment to 5.0.5 is the primary and only complete fix identified, and it should be prioritized for any Kylin instance reachable outside a trusted internal network, consistent with the vendor's own exposure guidance in the oss-security advisory (https://seclists.org/oss-sec/2026/q4/184) and the project site (https://kylin.apache.org/). Because the vendor frames public-network reachability as the core exploitation condition, the most effective compensating control where patching must be delayed is to stop exposing the Kylin REST API and Web UI to untrusted networks - front the service with a VPN, an IP allowlist, or a reverse proxy that performs an additional authentication layer; the trade-off is that legitimate remote analysts, BI tools (Tableau/Power BI/Excel connectors), and scheduled clients must be re-pointed through that gateway or granted source addresses, which adds operational overhead and can break external dashboards. Secondary controls: audit Kylin project membership and remove accounts from projects they no longer need, since exploitation requires at least one valid project-scoped account (PR:L per the assessed vector), and reduction of membership narrows the set of actors who can chain a cross-project request - at the cost of reduced collaboration for multi-team tenants. Review Kylin job engine logs and audit trails for job operations (resume, discard, status queries) against job IDs not owned by the requesting project, and alert on repeated authorization-shaped failures, accepting that Kylin's default logging may not record the requesting principal for every job operation, which limits retrospective detection. Note that the fix version 5.0.5 is taken from the vendor advisory and no independent backport for the 4.x line is confirmed in the provided data.
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 a distributed OLAP engine that pre-computes multidimensional cubes/models to deliver sub-second SQL analytics over very large datasets, with a REST/Web UI control plane that groups cubes, models, and their maintenance work into projects. The vulnerable component is JobController, the server-side handler that manages the lifecycle of asynchronous build/merge job submissions and exposes job operations through Kylin's job-management API. The flaw is a missing server-side ownership check: although requests are authenticated, the controller does not verify that the job identifier supplied by the caller belongs to a project the caller is a member of, so any authenticated principal can enumerate or act on jobs from other projects - an access-control class commonly mapped to CWE-862 (Missing Authorization) or CWE-639 (Authorization Bypass Through User-Controlled Key). No CWE identifier, CPE string, EPSS score, or vendor CVSS vector was supplied in the source data, so the assessed vector (PR:L, meaning an authenticated low-privileged actor) is the authoritative indication that at least one valid project account is required; the 'cross-project' framing in the advisory implies the actor has some legitimate Kylin access but exceeds its project boundary. Because integrity and availability impact are both low (I:L/A:L) with no confidentiality impact (C:N), the realistic effect is modification or disruption of other teams' build jobs rather than data exfiltration or full server compromise, and the vendor's stated precondition - the Kylin service being directly exposed to the public internet - remains the dominant exploitation limiter.
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 JobController (AV:N, AC:L); cross-project framing implies a low-privileged project account (PR:L); job tampering/cancellation yields integrity and availability impact (I:L/A:L), no clear confidentiality loss.
Description PRE-NVD
Executive ViewAI
Apache Kylin releases 4.0.0 through 5.0.4 contain an authorization gap in the JobController component that allows any user holding a valid account in one project to act on job records belonging to projects they are not a member of, weakening the integrity and availability of shared job workloads. The exposure requires an authenticated account, is limited to Kylin services directly reachable from the public network, and per the vendor leaves in-house, network-isolated deployments largely unaffected. Leadership should care because organizations relying on Kylin project boundaries as a multi-tenant separation control can no longer assume those boundaries hold, and teams whose Kylin instances face the internet carry the greatest exposure.
No vendor-released patch is identified in the advisory data at time of analysis, although the vendor states that upgrading to Apache Kylin 5.0.5 removes the condition and should be pursued as the remediation path. Interim mitigations: remove public network exposure for all Kylin instances in the 4.0.0 through 5.0.4 range so they are reachable only from trusted internal networks or via VPN, which aligns with the vendor's scoping of real-world impact to publicly reachable services; enforce strict least privilege and aggressive de-provisioning of Kylin accounts so that every authenticated user holds membership only in the projects they legitimately need; review and correct project membership rosters, and audit JobController job-operation logs for cross-project actions by non-members. Note that the issue requires an authenticated account (CVSS vector PR:L) and there is no public exploit code identified at time of analysis, so restricting who holds valid accounts and how those accounts reach the service materially reduces exposure while the 5.0.5 upgrade is scheduled.
Threat Intelligence Overview
CVE.org
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Exploit-DB