How severe is GHSA-f6m8-qm7j-fh65?

GHSA-f6m8-qm7j-fh65 has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-f6m8-qm7j-fh65?

GHSA-f6m8-qm7j-fh65 affects the following packages: org.apache.kylin:kylin (Maven), org.apache.kylin:kylin-common-server (Maven), org.apache.kylin:kylin-common-service (Maven), org.apache.kylin:kylin-core-common (Maven), org.apache.kylin:kylin-core-metadata (Maven), org.apache.kylin:kylin-ops-server (Maven), org.apache.kylin:kylin-server (Maven). Ecosystems affected: Maven.

How do I fix GHSA-f6m8-qm7j-fh65?

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-f6m8-qm7j-fh65 is resolved across your whole dependency graph.

How do I detect GHSA-f6m8-qm7j-fh65 in my Maven dependencies?

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.

How do I mitigate GHSA-f6m8-qm7j-fh65 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-f6m8-qm7j-fh65 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f6m8-qm7j-fh65 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-f6m8-qm7j-fh65?

GHSA-f6m8-qm7j-fh65 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-f6m8-qm7j-fh65?

GHSA-f6m8-qm7j-fh65 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-f6m8-qm7j-fh65 published, and has it been updated?

GHSA-f6m8-qm7j-fh65 was published on October 2, 2025 and was last updated on November 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

Apache Kylin Server-Side Request Forgery (SSRF) VulnerabilityGHSA-f6m8-qm7j-fh65

HIGHFix: apache/kylin#2332

GHSA-f6m8-qm7j-fh65 is a high-severity (CVSS 7.3) Server-Side Request Forgery (SSRF) vulnerability in org.apache.kylin:kylin. A fix is available for org.apache.kylin:kylin — see the affected versions and patch details below.

Also known asCVE-2025-61735

Published

Oct 2, 2025

Updated

Nov 5, 2025

Affected

7 pkgs

Patched

7 / 7

Exploits

None indexed

Exploitation data as of Nov 11, 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-f6m8-qm7j-fh65.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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

Server-Side Request Forgery (SSRF) vulnerability in Apache Kylin.

This issue affects Apache Kylin: from 4.0.0 through 5.0.2. You are fine as long as the Kylin's system and project admin access is well protected.

Users are recommended to upgrade to version 5.0.3, which fixes the issue.

Affected Packages

7 total 7 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.kylin:kylin`	≥ 4.0.0&&< 5.0.3	5.0.3`org.apache.kylin:kylin:5.0.3`
☕Maven	`org.apache.kylin:kylin-common-server`	≥ 4.0.0&&< 5.0.3	5.0.3`org.apache.kylin:kylin-common-server:5.0.3`
☕Maven	`org.apache.kylin:kylin-common-service`	≥ 4.0.0&&< 5.0.3	5.0.3`org.apache.kylin:kylin-common-service:5.0.3`
☕Maven	`org.apache.kylin:kylin-core-common`	≥ 4.0.0&&< 5.0.3	5.0.3`org.apache.kylin:kylin-core-common:5.0.3`
☕Maven	`org.apache.kylin:kylin-core-metadata`	≥ 4.0.0&&< 5.0.3	5.0.3`org.apache.kylin:kylin-core-metadata:5.0.3`
☕Maven	`org.apache.kylin:kylin-ops-server`	≥ 4.0.0&&< 5.0.3	5.0.3`org.apache.kylin:kylin-ops-server:5.0.3`

Affected Products

1 product · 1 configurations

Application

kylinapache

≥ 4.0.0 && < 5.0.3

range

Detection & mitigation playbook

Open-source dependency

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.
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-f6m8-qm7j-fh65 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

Server-Side Request Forgery (SSRF) vulnerability in Apache Kylin. This issue affects Apache Kylin: from 4.0.0 through 5.0.2. You are fine as long as the Kylin's system and project admin access is well protected. Users are recommended to upgrade to version 5.0.3, which fixes the issue.

O3 Security · Impact-Aware SCA

Is GHSA-f6m8-qm7j-fh65 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Raw vector

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

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Oct 2, 2025

Last updated

Nov 5, 2025

Identifiers

GHSA-f6m8-qm7j-fh65

References

Advisorynvd.nist.gov · CVE 2025 61735 Webgithub.com Webgithub.com · 22eb8fd5dfdeffa3fc57bae6d5c82a019eece662 Webissues.apache.org · KYLIN 6082 Weblists.apache.org · yscobmx869zvprsykb94r24jtmb58ckh Webopenwall.com Packagegithub.com · kylin

Related vulnerabilities

This CVE is high severity; 5 of 8 other CVEs affecting kylin are rated as high or higher (top: high).

CVE-2025-61735CVE-2025-61733CVE-2025-61734CVE-2025-30067CVE-2024-23590CVE-2022-43396CVE-2020-13937CVE-2021-36774

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedNov 5, 2025