Advisory record · GHSA-f6m8-qm7j-fh65

Apache Kylin Server-Side Request Forgery (SSRF) Vulnerability

CVSS 7.3 HighEPSS 0.010 · 63rd percentile

Published by the GitHub Advisory Database at 2 Oct 2025, 12:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.kylin:kylinMaven>=4.0.0, <5.0.35.0.3
org.apache.kylin:kylin-common-serverMaven>=4.0.0, <5.0.35.0.3
org.apache.kylin:kylin-common-serviceMaven>=4.0.0, <5.0.35.0.3
org.apache.kylin:kylin-core-commonMaven>=4.0.0, <5.0.35.0.3
org.apache.kylin:kylin-core-metadataMaven>=4.0.0, <5.0.35.0.3
org.apache.kylin:kylin-ops-serverMaven>=4.0.0, <5.0.35.0.3
org.apache.kylin:kylin-serverMaven>=4.0.0, <5.0.35.0.3
Identifiers
GHSA-f6m8-qm7j-fh65 · CVE-2025-61735
Weakness (CWE)
CWE-918
Published
2 Oct 2025
Updated
5 Nov 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Kylin versions 4.0.0 through 5.0.2 are affected by a Server-Side Request Forgery vulnerability, and the fix is in 5.0.3. The source does not describe the attacker's required access in detail beyond stating that the risk depends on protecting Kylin's system and project admin access. Users should upgrade to Apache Kylin 5.0.3.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.3 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.010, the 63rd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:09 UTC First seen by agentprime
  2. 31 Oct 2026, 15:09 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.