VulnerabilityPublished 2 Oct 2025Updated 4 Nov 2025

CVE-2025-61734: Apache Kylin · Exposed Files or Directories

Affects Apache KylinSource CVE Database V5

Not known to be exploited · 26% EPSS · CVSS 7.5 High · fixed in 5.0.3 : patch Apache Kylin soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 26.1% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Apache Software Foundation Apache Kylin	Affected =4.0.0	Fixed in–

AI-suggested

Upgrade Apache Kylin to version 5.0.3 or later immediately to apply the official fix for CVE-2025-61734.
Restrict network access to Apache Kylin instances by implementing strict firewall rules and network segmentation to limit exposure to trusted internal networks only.
Enforce strong authentication and authorization policies for Kylin administrative and project access to reduce the risk of lateral movement if external access occurs.
Conduct regular audits of file and directory permissions within Kylin deployments to ensure no sensitive files are inadvertently exposed.
Monitor logs and network traffic for unusual access patterns or attempts to access unauthorized files or directories.
Employ web application firewalls (WAFs) or intrusion detection/prevention systems (IDS/IPS) with rules tailored to detect exploitation attempts targeting Kylin.
Educate system administrators and security teams about this vulnerability and the importance of timely patching and access control enforcement.
Review and update incident response plans to include scenarios involving unauthorized data access through analytics platforms like Apache Kylin.

Description

Files or Directories Accessible to External Parties vulnerability in Apache Kylin. You are fine as long as the Kylin's system and project admin access is well protected. This issue affects Apache Kylin: from 4.0.0 through 5.0.2. Users are recommended to upgrade to version 5.0.3, which fixes the issue.

Impact

For European organizations, the primary impact of CVE-2025-61734 is the potential unauthorized disclosure of sensitive data processed or stored within Apache Kylin environments. This could include proprietary business intelligence data, personally identifiable information (PII), or other confidential analytics results. Data leakage can lead to regulatory non-compliance, especially under GDPR, resulting in legal penalties and reputational damage. Sectors such as finance, telecommunications, healthcare, and government agencies that rely heavily on big data analytics are particularly vulnerable. The vulnerability does not affect system integrity or availability, so operational disruptions are unlikely. However, the ease of exploitation without authentication increases the risk of widespread data exposure if unpatched systems are accessible from external networks. Organizations with weak perimeter defenses or misconfigured network access controls are at higher risk. The lack of known exploits in the wild provides a window for proactive mitigation, but the high CVSS score (7.5) reflects the critical need for timely patching and monitoring.

Summary

CVE-2025-61734 is a vulnerability classified under CWE-552, indicating that files or directories are accessible to external parties without proper authorization in Apache Kylin versions 4.0.0 through 5.0.2. Apache Kylin is an open-source distributed analytics engine designed for big data, widely used for OLAP on Hadoop and other big data platforms. The vulnerability allows remote attackers to access sensitive files or directories without requiring any authentication or user interaction, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). This means an attacker can exploit the flaw over the network with low complexity and no privileges. The impact is primarily on confidentiality, as unauthorized access to files could lead to data leakage, including potentially sensitive configuration files, user data, or analytics results. Integrity and availability are not directly affected. The vulnerability is mitigated in Apache Kylin version 5.0.3, which includes fixes to restrict unauthorized access. While no exploits are currently known in the wild, the vulnerability's characteristics make it a significant risk, especially in environments where Kylin's administrative access controls are not tightly secured. The issue underscores the importance of upgrading to the patched version and implementing robust access controls to prevent unauthorized external access to internal resources.

CWE-552Files or Directories Accessible to External Parties (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product makes files or directories accessible to unauthorized actors, even though they should not be.
Implementation · System Configuration · Operation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.1 (opens in a new tab)
V12.4.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
Attack patterns
Collect Data from Common Resource Locations (opens in a new tab)
Probe System Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 22:15 UTC

WeaknessesCWE-552

Technical details

References

Community reviews

Related threats