cve.bz

CVE-2025-61734 apache kylin

7.5 highEPSS 29%Fix available

High (7.5) in apache kylin. EPSS 29% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.kylin:kylin 5.0.3.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
29% (unchanged from 28% a week ago; 20% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-10-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-552 Files or Directories Accessible to External Parties
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • org.apache.kylin:kylin (Maven): fixed in 5.0.3
  • org.apache.kylin:kylin-common-server (Maven): fixed in 5.0.3
  • org.apache.kylin:kylin-common-service (Maven): fixed in 5.0.3
  • org.apache.kylin:kylin-core-common (Maven): fixed in 5.0.3
  • org.apache.kylin:kylin-core-metadata (Maven): fixed in 5.0.3
  • org.apache.kylin:kylin-ops-server (Maven): fixed in 5.0.3
  • org.apache.kylin:kylin-server (Maven): fixed in 5.0.3
  • Vendor advisory: https://lists.apache.org/thread/z705g7sn3g0bkchlqbo1hz1tyqorn4d2

Ask an AI about this CVE

Show the promptExplain CVE-2025-61734 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-61734?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-61734?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-61734 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-61734

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-61734](https://cve.bz/cve/badge/CVE-2025-61734.svg)](https://cve.bz/cve/CVE-2025-61734)

HTML:

<a href="https://cve.bz/cve/CVE-2025-61734"><img src="https://cve.bz/cve/badge/CVE-2025-61734.svg" alt="CVE-2025-61734"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Kylinfrom 4.0.0 through 5.0.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p86w-w5rh-m3hxMavenorg.apache.kylin:kylin>=4.0.0 <5.0.35.0.3
GHSA-p86w-w5rh-m3hxMavenorg.apache.kylin:kylin-common-server>=4.0.0 <5.0.35.0.3
GHSA-p86w-w5rh-m3hxMavenorg.apache.kylin:kylin-common-service>=4.0.0 <5.0.35.0.3
GHSA-p86w-w5rh-m3hxMavenorg.apache.kylin:kylin-core-common>=4.0.0 <5.0.35.0.3
GHSA-p86w-w5rh-m3hxMavenorg.apache.kylin:kylin-core-metadata>=4.0.0 <5.0.35.0.3
GHSA-p86w-w5rh-m3hxMavenorg.apache.kylin:kylin-ops-server>=4.0.0 <5.0.35.0.3
GHSA-p86w-w5rh-m3hxMavenorg.apache.kylin:kylin-server>=4.0.0 <5.0.35.0.3

Attack patterns (CAPEC)

  • CAPEC-150 Collect Data from Common Resource Locations Severity: Medium
  • CAPEC-639 Probe System Files Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON