NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Keycloak allows anyone to register new security device or key for any user by using WebAuthn password-less login flowGHSA-qpq9-jpv4-6gwr

HIGHFix: keycloak/keycloak#8203

GHSA-qpq9-jpv4-6gwr is a high-severity (CVSS 7.5) Improper Authentication vulnerability in org.keycloak:keycloak-core. A fix is available for org.keycloak:keycloak-core — see the affected versions and patch details below.

Also known asCVE-2021-3632
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk
0.00%0.55%1.11%1.66%0.5%1.2%May 26Sep 26Nov 26

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

1 pkg affected
☕org.keycloak:keycloak-core

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. This vulnerability allows anyone to register a new security device or key when there is not a device already registered for any user by using the WebAuthn password-less login flow.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-coreall versions15.1.0org.keycloak:keycloak-core:15.1.0

Affected Products

2 products · 3 configurations
Application
keycloakredhat
< 15.1.0
range
Application
single sign-onredhat
≥ 7.4 && < 7.4.9
1 version
7.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. Fix

    Update org.keycloak:keycloak-core to 15.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qpq9-jpv4-6gwr is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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 HatModerate
ProductFixed inAdvisory
Red Hat Single Sign-On 7.4.9see advisoryRHSA-2021:3534
Red Hat Single Sign-On 7.4 for RHEL 6rh-sso7-keycloak-0:9.0.15-1.redhat_00002.1.el6ssoRHSA-2021:3527
Red Hat Single Sign-On 7.4 for RHEL 7rh-sso7-keycloak-0:9.0.15-1.redhat_00002.1.el7ssoRHSA-2021:3528
Red Hat Single Sign-On 7.4 for RHEL 8rh-sso7-keycloak-0:9.0.15-1.redhat_00002.1.el8ssoRHSA-2021:3529

Frequently Asked Questions

A flaw was found in Keycloak. This vulnerability allows anyone to register a new security device or key when there is not a device already registered for any user by using the WebAuthn password-less login flow.
O3 Security · Impact-Aware SCA

Is GHSA-qpq9-jpv4-6gwr in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Keycloak allows anyone to register new security device or…