How severe is GHSA-wrx7-qgmj-mf2q?

No CVSS score has been assigned to GHSA-wrx7-qgmj-mf2q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wrx7-qgmj-mf2q?

GHSA-wrx7-qgmj-mf2q affects the following packages: org.apache.kylin:kylin (Maven). Ecosystems affected: Maven.

How do I fix GHSA-wrx7-qgmj-mf2q?

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

How do I detect GHSA-wrx7-qgmj-mf2q in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.kylin:kylin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wrx7-qgmj-mf2q if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-wrx7-qgmj-mf2q?

O3 pinpoints whether GHSA-wrx7-qgmj-mf2q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wrx7-qgmj-mf2q actively exploited in the wild?

No public exploit code has been indexed for GHSA-wrx7-qgmj-mf2q 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-wrx7-qgmj-mf2q?

GHSA-wrx7-qgmj-mf2q has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 84th 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-wrx7-qgmj-mf2q?

GHSA-wrx7-qgmj-mf2q 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-wrx7-qgmj-mf2q published, and has it been updated?

GHSA-wrx7-qgmj-mf2q was published on January 8, 2022 and was last updated on December 4, 2024. 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

GHSA-wrx7-qgmj-mf2q

Fix: apache/kylin#1646

GHSA-wrx7-qgmj-mf2q is a Server-Side Request Forgery (SSRF) vulnerability in org.apache.kylin:kylin. O3 Security confirms whether GHSA-wrx7-qgmj-mf2q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Server-Side Request Forgery in Apache Kylin

Also known asCVE-2021-27738

Published

Jan 8, 2022

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% 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.

Real-World Exposure

1 pkg affected

☕org.apache.kylin:kylin

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

All request mappings in StreamingCoordinatorController.java handling /kylin/api/streaming_coordinator/* REST API endpoints did not include any security checks, which allowed an unauthenticated user to issue arbitrary requests, such as assigning/unassigning of streaming cubes, creation/modification and deletion of replica sets, to the Kylin Coordinator. For endpoints accepting node details in HTTP message body, unauthenticated (but limited) server-side request forgery (SSRF) can be achieved. This issue affects Apache Kylin Apache Kylin 3 versions prior to 3.1.2.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.kylin:kylin`	all versions	3.1.3

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.kylin:kylin to 3.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wrx7-qgmj-mf2q is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-wrx7-qgmj-mf2q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

All request mappings in `StreamingCoordinatorController.java` handling `/kylin/api/streaming_coordinator/*` REST API endpoints did not include any security checks, which allowed an unauthenticated user to issue arbitrary requests, such as assigning/unassigning of streaming cubes, creation/modification and deletion of replica sets, to the Kylin Coordinator. For endpoints accepting node details in HTTP message body, unauthenticated (but limited) server-side request forgery (SSRF) can be achieved. This issue affects Apache Kylin Apache Kylin 3 versions prior to 3.1.2.

O3 Security · Impact-Aware SCA

Is GHSA-wrx7-qgmj-mf2q in your dependencies?

O3 detects GHSA-wrx7-qgmj-mf2q across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works