Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

GHSA-p86w-w5rh-m3hx — kylin

HIGHFix: apache/kylin#2332

GHSA-p86w-w5rh-m3hx is a high-severity (CVSS 7.5) CWE-552 vulnerability in org.apache.kylin:kylin. EPSS puts its 30-day exploitation probability at 19.8% (97th percentile). A fix is available for org.apache.kylin:kylin — see the affected versions and patch details below.

Apache Kylin Files or Directories Accessible to External Parties

Also known asCVE-2025-61734
Published
Oct 2, 2025
Updated
Nov 5, 2025
Affected
7 pkgs
Patched
7 / 7
Exploits
None indexed
Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-p86w-w5rh-m3hx.

EPSS Exploitation Probability

via FIRST.org ↗
19.8%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-p86w-w5rh-m3hx plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

7 pkgs affected
☕org.apache.kylin:kylin☕org.apache.kylin:kylin-common-server☕org.apache.kylin:kylin-common-service☕org.apache.kylin:kylin-core-common☕org.apache.kylin:kylin-core-metadata☕org.apache.kylin:kylin-ops-server☕org.apache.kylin:kylin-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.kylin:kylin≥ 4.0.0&&< 5.0.35.0.3org.apache.kylin:kylin:5.0.3
☕Mavenorg.apache.kylin:kylin-common-server≥ 4.0.0&&< 5.0.35.0.3org.apache.kylin:kylin-common-server:5.0.3
☕Mavenorg.apache.kylin:kylin-common-service≥ 4.0.0&&< 5.0.35.0.3org.apache.kylin:kylin-common-service:5.0.3
☕Mavenorg.apache.kylin:kylin-core-common≥ 4.0.0&&< 5.0.35.0.3org.apache.kylin:kylin-core-common:5.0.3
☕Mavenorg.apache.kylin:kylin-core-metadata≥ 4.0.0&&< 5.0.35.0.3org.apache.kylin:kylin-core-metadata:5.0.3
☕Mavenorg.apache.kylin:kylin-ops-server≥ 4.0.0&&< 5.0.35.0.3org.apache.kylin:kylin-ops-server:5.0.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.kylin:kylin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.kylin:kylin to 5.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p86w-w5rh-m3hx is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p86w-w5rh-m3hx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-p86w-w5rh-m3hx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-p86w-w5rh-m3hx in your dependencies?

O3 Security finds GHSA-p86w-w5rh-m3hx across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-p86w-w5rh-m3hx: kylin (High 7.5) | O3 Security