GHSA-cm29-6wx7-p874 — keycloak-parent
HIGHGHSA-cm29-6wx7-p874 is a high-severity (CVSS 7.1) CWE-613 vulnerability in org.keycloak:keycloak-parent. A fix is available for org.keycloak:keycloak-parent — see the affected versions and patch details below.
Keycloak insufficient session expiration
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-cm29-6wx7-p874 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 378,567 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-parentReal-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 keycloak may fail to logout user session if the logout request comes from external SAML identity provider and Principal Type is set to Attribute [Name].
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-parent | all versions | 14.0.0org.keycloak:keycloak-parent:14.0.0 |
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-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-parent to 14.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cm29-6wx7-p874 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-cm29-6wx7-p874 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-cm29-6wx7-p874. 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.4.7 | see advisory | RHSA-2021:2070 |
| Red Hat Single Sign-On 7.4 for RHEL 6 | rh-sso7-keycloak-0:9.0.13-1.redhat_00006.1.el6sso | RHSA-2021:2063 |
| Red Hat Single Sign-On 7.4 for RHEL 7 | rh-sso7-keycloak-0:9.0.13-1.redhat_00006.1.el7sso | RHSA-2021:2064 |
| Red Hat Single Sign-On 7.4 for RHEL 8 | rh-sso7-keycloak-0:9.0.13-1.redhat_00006.1.el8sso | RHSA-2021:2065 |
Frequently Asked Questions
Is GHSA-cm29-6wx7-p874 in your dependencies?
O3 Security finds GHSA-cm29-6wx7-p874 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.