dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2025-3910

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-29
Fix available
A fix is available. Upgrade to 26.0.11 or later.
See remediation →
61/100
Remediation priority · Elevated
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. The org.keycloak.authorization package may be vulnerable to circumventing required actions, allowing users to circumvent requirements such as setting up two-factor authentication.

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 · moderate confidence

The org.keycloak.authorization package in Keycloak contains a flaw that allows authenticated users to bypass required actions such as two-factor authentication setup. This authorization bypass occurs when the system fails to properly enforce required actions before granting access to protected resources.

MitigationOrganizations using Keycloak should monitor for vendor security advisories and apply patches when available. In the interim, implement additional access controls and monitor for unauthorized access patterns that may indicate exploitation of this bypass.

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.0, < 26.0.11

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 the installed Keycloak version
    Check the Keycloak server version by querying the /health/ready endpoint, viewing the startup logs, or running 'kc.sh show-version' (for the Keycloak container/instance)
    Affected if The version is >= 26.0.0 and < 26.0.11 (specifically any version from 26.0 up to but not including 26.0.11)
  2. Verify if required actions are configured in authentication flows
    Navigate to the Keycloak Admin Console, go to Authentication > Flows, and review the configured authentication flows to see if any required actions (such as 'Configure OTP', 'Terms and Conditions', or other required actions) are defined
    Affected if Required actions are assigned but may not be properly enforced before resource access is granted due to the authorization bypass in the org.keycloak.authorization package
  3. Inspect authentication flow bindings
    Go to Authentication > Bindings in the Admin Console and check which authentication flow is set as the 'Browser Flow' and 'Direct Grant Flow', then examine those flows for required action configuration
    Affected if The flows contain required action executors but the org.keycloak.authorization component fails to enforce them before granting access to protected resources
  4. Review realm authentication settings
    Navigate to Realm Settings > Login in the Admin Console and check if 'Required Actions' are enabled (such as 'Configure OTP' for two-factor authentication)
    Affected if Required actions are enabled in the realm settings but the authorization layer bypasses their enforcement for authenticated users accessing protected resources

A user is affected if they are running Redhat Build of Keycloak versions 26.0.0 through 26.0.11 and have required actions (like 2FA setup) configured in their authentication flows, as the org.keycloak.authorization package fails to properly enforce these actions.

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.0.11 or later
Fixed in 26.0.11
Interim mitigation

Organizations using Keycloak should monitor for vendor security advisories and apply patches when available. In the interim, implement additional access controls and monitor for unauthorized access patterns that may indicate exploitation of this bypass.

Recommended fix High confidence

26.0.11 or later

  1. 1. Back up your current Keycloak installation and database
  2. 2. Download Keycloak version 26.0.11 or later from the official Keycloak releases page (github.com/keycloak/keycloak/releases)
  3. 3. Upgrade your Keycloak instance to version 26.0.11 or later following the standard upgrade documentation
  4. 4. Verify that the org.keycloak.authorization package properly enforces required actions such as 2FA setup
  5. 5. Test that users can no longer bypass required actions after the upgrade
  6. 6. Monitor logs for any authentication-related anomalies
Caveat Review release notes for 26.0.11+ for any security-related configuration changes that may affect your deployment

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

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3910 — 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-2025-3910 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