dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-37982

MEDIUM · 6.8 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 26.4.12 or later.
See remediation →
75/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in Keycloak. This authentication vulnerability allows a remote attacker to replay `ExecuteActionsActionToken` tokens within Keycloak's WebAuthn (Web Authentication) flow. By intercepting an execute-actions email link, an attacker can register their own authenticator to a victim's account. This leads to unauthorized enrollment of a hardware-backed credential, enabling persistent account takeover.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Keycloak suffers from a token replay vulnerability in its WebAuthn flow where ExecuteActionsActionToken tokens can be replayed by attackers who intercept the execute-actions email link. This allows the attacker to register their own hardware-backed authenticator to the victim's account, achieving persistent account takeover.

MitigationImplement token replay protection by ensuring ExecuteActionsActionToken tokens are single-use, properly expire, and validate token uniqueness during the WebAuthn enrollment flow. Additionally, consider implementing additional email verification steps before allowing WebAuthn credential enrollment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of KeycloakApplication
Affected:>= 26.4, < 26.4.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Keycloak version
    Check the installed version of Red Hat Build of Keycloak by reviewing the RPM package (rpm -q) or the $KEYCLOAK_HOME/src/main/resources/product.xml file, or by querying the Keycloak admin console server info endpoint
    Affected if The installed version is greater than or equal to 26.4 but less than 26.4.12
  2. Confirm WebAuthn authentication is enabled
    In Keycloak admin console, navigate to Authentication > Flows and verify if the WebAuthn Authenticator flow is active, or check realm configuration files for webauthn-enabled: true settings
    Affected if WebAuthn authentication is enabled in the realm configuration
  3. Verify ExecuteActionsActionToken configuration
    Check the Keycloak realm configuration or authentication flow settings for ExecuteActionsActionToken token settings. This can be done via the admin REST API at /admin/realms/{realm} or by inspecting the keycloak-server.json configuration
    Affected if ExecuteActionsActionToken is configured without single-use enforcement or replay protection for WebAuthn enrollment flows
  4. Inspect email action token settings
    Review the token lifecycle settings in the Keycloak server configuration (keycloak-server.json or standalone.xml) for action token validity periods and replay protection settings related to the execute-actions endpoint
    Affected if Token replay protection is not explicitly configured or is disabled for action tokens used in WebAuthn enrollment

You are affected if you run Red Hat Build of Keycloak versions 26.4 through 26.4.11 with WebAuthn authentication enabled and the ExecuteActionsActionToken lacks proper single-use replay protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 26.4.12 or later
Fixed in 26.4.12
Interim mitigation

Implement token replay protection by ensuring ExecuteActionsActionToken tokens are single-use, properly expire, and validate token uniqueness during the WebAuthn enrollment flow. Additionally, consider implementing additional email verification steps before allowing WebAuthn credential enrollment.

Recommended fix High confidence

Keycloak 26.4.12

  1. Upgrade Keycloak to version 26.4.12 or later to remediate this vulnerability
  2. After upgrading, review all ExecuteActionsActionToken email flows to ensure no malicious authenticator registrations occurred
  3. As a security precaution, consider invalidating and re-registering WebAuthn credentials for affected users
  4. Monitor for any unauthorized authenticator enrollments in audit logs

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-37982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-37982 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data