How severe is CVE-2026-37982?

No CVSS score has been assigned to CVE-2026-37982 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-37982?

CVE-2026-37982 affects the following packages: keycloak (Bitnami). Ecosystems affected: Bitnami.

How do I fix CVE-2026-37982?

Update keycloak to 26.4.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-37982 is resolved across your whole dependency graph.

How do I detect CVE-2026-37982 in my Bitnami dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keycloak, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-37982 if there is no patch (or I can't update yet)?

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.

Is CVE-2026-37982 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-37982 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-37982?

CVE-2026-37982 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 45th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-37982?

CVE-2026-37982 is classified as CWE-294 (CWE-294). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-37982 published, and has it been updated?

CVE-2026-37982 was published on August 25, 2026 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

CVE-2026-37982 — keycloak

CVE-2026-37982 is a CWE-294 vulnerability in keycloak. A fix is available for keycloak — see the affected versions and patch details below.

Keycloak: org.keycloak.authentication: keycloak: unauthorized account takeover via webauthn token replay

Also known asGHSA-w4p5-rfh6-cwrv

Published

Aug 25, 2026

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-37982.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦keycloak

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Bitnami packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`keycloak`	≥ 26.4.0&&< 26.4.12	26.4.12

Affected Products

1 product · 1 configurations

Application

build of keycloakredhat

≥ 26.4 && < 26.4.12

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keycloak, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update keycloak to 26.4.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-37982 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.

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

This vulnerability has a Moderate impact on Red Hat Build of Keycloak (RHBK). A flaw in Keycloak's WebAuthn flow allows an attacker who gains access to an execute-actions email link to replay tokens containing WEBAUTHN_REGISTER or WEBAUTHN_PASSWORDLESS_REGISTER. This enables unauthorized WebAuthn registration with the…

Workaround published by Red Hat

To mitigate this issue, consider disabling WebAuthn required actions in Keycloak if they are not essential for your deployment. This will prevent the vulnerable token replay mechanism from being exploited. Consult Keycloak documentation for specific configuration steps to disable WebAuthn required actions. Note that applying configuration changes may require a service restart and could impact functionality relying on WebAuthn registration.

Source: Red Hat security advisory for CVE-2026-37982 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat build of Keycloak 26.4	`rhbk/keycloak-operator-bundle:26.4.12-1`	RHSA-2026:19597
Red Hat build of Keycloak 26.4.12	`rhbk/keycloak-rhel9`	RHSA-2026:19596

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2026-37982 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works