How severe is GHSA-m6q9-p373-g5q8?

GHSA-m6q9-p373-g5q8 has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-m6q9-p373-g5q8?

GHSA-m6q9-p373-g5q8 affects the following packages: org.keycloak:keycloak-services (Maven), org.keycloak:keycloak-services (Maven). Ecosystems affected: Maven.

How do I fix GHSA-m6q9-p373-g5q8?

Update org.keycloak:keycloak-services to 22.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6q9-p373-g5q8 is resolved across your whole dependency graph.

How do I detect GHSA-m6q9-p373-g5q8 in my Maven dependencies?

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

How do I mitigate GHSA-m6q9-p373-g5q8 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.

Is GHSA-m6q9-p373-g5q8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m6q9-p373-g5q8 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-m6q9-p373-g5q8?

GHSA-m6q9-p373-g5q8 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 39th 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-m6q9-p373-g5q8?

GHSA-m6q9-p373-g5q8 is classified as CWE-346 (CWE-346). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m6q9-p373-g5q8 published, and has it been updated?

GHSA-m6q9-p373-g5q8 was published on April 17, 2024 and was last updated on September 10, 2026. 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

Keycloak's unvalidated cross-origin messages in checkLoginIframe leads to DDoSGHSA-m6q9-p373-g5q8

HIGHFix: keycloak/keycloak@9d9817e

GHSA-m6q9-p373-g5q8 is a high-severity (CVSS 7.4) CWE-346 vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.

Also known asCVE-2024-1249

Published

Apr 17, 2024

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 7, 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-m6q9-p373-g5q8.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% 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

2 pkgs affected

☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services

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

A potential security flaw in the "checkLoginIframe" which allows unvalidated cross-origin messages, enabling potential DDoS attacks. By exploiting this vulnerability, attackers could coordinate to send millions of requests in seconds using simple code, significantly impacting the application's availability without proper origin validation for incoming messages.

Acknowledgements

Special thanks to Adriano Márcio Monteiro from BRZTEC for reporting this issue and helping us improve our project.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.keycloak:keycloak-services`	all versions	22.0.10`org.keycloak:keycloak-services:22.0.10`
☕Maven	`org.keycloak:keycloak-services`	≥ 23.0.0&&< 24.0.3	24.0.3`org.keycloak:keycloak-services:24.0.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.keycloak:keycloak-services, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-services to 22.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6q9-p373-g5q8 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

The vulnerability in Keycloak's OIDC component allowing unvalidated cross-origin messages in the "checkLoginIframe" function represents an important severity issue due to its potential to cause significant disruption and resource exhaustion. Exploitation of this flaw can lead to a Denial of Service (DoS) condition,…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-m6q9-p373-g5q8 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat AMQ Broker 7	`keycloak`	RHSA-2024:2945
Red Hat build of Keycloak 22	`rhbk/keycloak-operator-bundle:22.0.10-1`	RHSA-2024:1867
Red Hat build of Keycloak 22.0.10	`keycloak`	RHSA-2024:1868
Red Hat Single Sign-On 7.6 for RHEL 7	`rh-sso7-keycloak-0:18.0.13-1.redhat_00001.1.el7sso`	RHSA-2024:1860
Red Hat Single Sign-On 7.6 for RHEL 8	`rh-sso7-keycloak-0:18.0.13-1.redhat_00001.1.el8sso`	RHSA-2024:1861
Red Hat Single Sign-On 7.6 for RHEL 9	`rh-sso7-keycloak-0:18.0.13-1.redhat_00001.1.el9sso`	RHSA-2024:1862
RHEL-8 based Middleware Containers	`rh-sso-7/sso76-openshift-rhel8:7.6-46`	RHSA-2024:1864
RHOSS-1.33-RHEL-8	`openshift-serverless-1/logic-data-index-ephemeral-rhel8:1.33.0-5`	RHSA-2024:4057

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-m6q9-p373-g5q8 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works