GHSA-3qh2-mccc-q5m6 — keycloak-core
MEDIUMGHSA-3qh2-mccc-q5m6 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in org.keycloak:keycloak-core. No vendor fix is recorded yet; mitigation options are listed below.
Keycloak Open Redirect
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-3qh2-mccc-q5m6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.keycloak:keycloak-coreReal-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 JBOSS Keycloak 3.2.1.Final. The Redirect URL for both Login and Logout are not normalized in org.keycloak.protocol.oidc.utils.RedirectUtils before the redirect url is verified. This can lead to an Open Redirection attack
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-core | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of org.keycloak:keycloak-core has shipped for GHSA-3qh2-mccc-q5m6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-3qh2-mccc-q5m6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-3qh2-mccc-q5m6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Single Sign-On 7.2.5 zip | see advisory | RHSA-2018:3595 |
| Red Hat Single Sign-On 7.2 for RHEL 6 | rh-sso7-keycloak-0:3.4.14-1.Final_redhat_00001.1.jbcs.el6 | RHSA-2018:3592 |
| Red Hat Single Sign-On 7.2 for RHEL 7 | rh-sso7-keycloak-0:3.4.14-1.Final_redhat_00001.1.jbcs.el7 | RHSA-2018:3593 |
Frequently Asked Questions
Is GHSA-3qh2-mccc-q5m6 in your dependencies?
O3 Security finds GHSA-3qh2-mccc-q5m6 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.