How severe is GHSA-mwm4-5qwr-g9pf?

No CVSS score has been assigned to GHSA-mwm4-5qwr-g9pf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mwm4-5qwr-g9pf?

GHSA-mwm4-5qwr-g9pf affects the following packages: org.keycloak:keycloak-services (Maven). Ecosystems affected: Maven.

How do I fix GHSA-mwm4-5qwr-g9pf?

Update org.keycloak:keycloak-services to 18.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mwm4-5qwr-g9pf is resolved across your whole dependency graph.

How do I detect GHSA-mwm4-5qwr-g9pf 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-mwm4-5qwr-g9pf 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-mwm4-5qwr-g9pf?

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

Is GHSA-mwm4-5qwr-g9pf actively exploited in the wild?

No public exploit code has been indexed for GHSA-mwm4-5qwr-g9pf 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.

When was GHSA-mwm4-5qwr-g9pf published, and has it been updated?

GHSA-mwm4-5qwr-g9pf was published on April 28, 2022 and was last updated on November 28, 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-mwm4-5qwr-g9pf — keycloak-services

Fix: keycloak/keycloak@ac79fd0

GHSA-mwm4-5qwr-g9pf is a security vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.

Keycloak is vulnerable to IDN homograph attack

Published

Apr 28, 2022

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 28, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕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 flaw was found in keycloak, where IDN homograph attacks are possible. This flaw allows a malicious user to register a name that already exists and then tricking an admin to grant extra privileges. The highest threat from this vulnerability is to integrity.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.keycloak:keycloak-services`	all versions	18.0.0`org.keycloak:keycloak-services:18.0.0`

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 18.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mwm4-5qwr-g9pf 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mwm4-5qwr-g9pf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mwm4-5qwr-g9pf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-mwm4-5qwr-g9pf in your dependencies?

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

Scan my dependencies How O3 SCA works