NVD / CVE Program· CNA redhat

CVE-2021-3632: A flaw was found in Keycloak.

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.1% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
Fixed version: org.keycloak:keycloak-core (Maven) 15.1.0; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.15-1.redhat_00002.1.el6sso; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.15-1.redhat_00002.1.el6sso.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to org.keycloak:keycloak-core (Maven) 15.1.0; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.15-1.redhat_00002.1.el6sso; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7::el6) 0:9.0.15-1.redhat_00002.1.el6sso or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Aug 26, 2022
Updated: Jun 17, 2026
EPSS: 1.1% · 67th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
redhat	keycloak	cpe:2.3:a:redhat:keycloak
redhat	single sign-on	cpe:2.3:a:redhat:single_sign-on
redhat	enterprise linux	cpe:2.3:o:redhat:enterprise_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

redhat keycloakbefore 15.1.0
redhat single sign-on7.4 and later · before 7.4.9
redhat single sign-on7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

n/a keycloak
- Fixed in v15.1.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.keycloak:keycloak-core	before 15.1.0	15.1.0
Red Hat:red_hat_single_sign_on:7::el6	rh-sso7-keycloak	before 0:9.0.15-1.redhat_00002.1.el6sso	0:9.0.15-1.redhat_00002.1.el6sso
Red Hat:red_hat_single_sign_on:7::el6	rh-sso7-keycloak-server	before 0:9.0.15-1.redhat_00002.1.el6sso	0:9.0.15-1.redhat_00002.1.el6sso
Red Hat:red_hat_single_sign_on:7::el7	rh-sso7-keycloak	before 0:9.0.15-1.redhat_00002.1.el7sso	0:9.0.15-1.redhat_00002.1.el7sso
Red Hat:red_hat_single_sign_on:7::el7	rh-sso7-keycloak-server	before 0:9.0.15-1.redhat_00002.1.el7sso	0:9.0.15-1.redhat_00002.1.el7sso
Red Hat:red_hat_single_sign_on:7::el8	rh-sso7-keycloak	before 0:9.0.15-1.redhat_00002.1.el8sso	0:9.0.15-1.redhat_00002.1.el8sso
Red Hat:red_hat_single_sign_on:7::el8	rh-sso7-keycloak-server	before 0:9.0.15-1.redhat_00002.1.el8sso	0:9.0.15-1.redhat_00002.1.el8sso

Same product

redhat: all records

Other highest-scoring records for the same primary product.

CVE-2020-10770A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using the OIDC parameter
42Plan
CVE-2022-1245A privilege escalation flaw was found in the token exchange feature of keycloak.
39Monitor
CVE-2019-14910A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS fro
39Monitor

Published before and after this one in the same product

← EarlierCVE-2020-35509Aug 23, 2022 · A flaw was found in keycloak affecting versions 11.0.3 and 12.0.0.
21Monitor
← EarlierCVE-2021-3827Aug 23, 2022 · A flaw was found in keycloak, where the default ECP binding flow allows other authentication flows to be bypassed.
27Monitor
Later →CVE-2021-3754Aug 26, 2022 · A flaw was found in keycloak where an attacker is able to register himself with the username same as the email ID of any existing user.
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Maven:org.keycloak:keycloak-core	15.1.0	Package registry (OSV)
red hat:rh-sso7-keycloak	0:9.0.15-1.redhat_00002.1.el6sso · Red Hat:red_hat_single_sign_on:7::el6	Package registry (OSV)
red hat:rh-sso7-keycloak-server	0:9.0.15-1.redhat_00002.1.el6sso · Red Hat:red_hat_single_sign_on:7::el6	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-21-0737 · Sep 15, 2021(RedHat Güvenlik Güncellemesi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
A user must open a link or visit a page.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

access.redhat.com/security/cve/CVE-2021-3632

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records