CVE-2025-3910: Org.keycloak.authentication: two factor authentication bypass

Published Apr 23, 2025
·
Updated

Description 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.

Other sources

AIA (Application-initiated actions) could be used to circumvent required actions configured by an administrator to be performed by a user upon signing in. This could lead to the user circumventing requirements such as setting up 2FA.

- A user account that has been required by an administrator to perform a required action. - The same user passing in a URL parameter during the sign in process.

Red Hat

Affected Software

4 affected componentsFixes available
Keycloak Keycloak
maven/org.keycloak:keycloak-services<26.2.2
26.2.2
redhat Build Of Keycloak>=26.0<26.0.11
IBM Concert Software<=1.0.0-2.1.0

Event History

Apr 23, 2025
Data Sourced
via Red Hat·07:29 PM
DescriptionSeverityAffected Software
Apr 29, 2025
CVE Published
via MITRE·08:46 PM
Data Sourced
via MITRE·08:46 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
Affected Software
Apr 30, 2025
Advisory Published
via GitHub·05:26 PM
Data Sourced
via GitHub·05:26 PM
DescriptionSeverityWeaknessAffected Software
Dec 22, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-3910?

CVE-2025-3910 is considered a critical vulnerability due to its potential to allow unauthorized circumvention of required security actions.

2

How do I fix CVE-2025-3910?

To mitigate CVE-2025-3910, update your Keycloak installation to the latest version that addresses this vulnerability.

3

What systems are affected by CVE-2025-3910?

CVE-2025-3910 affects installations of Keycloak, particularly those using the org.keycloak.authorization package.

4

What are the implications of CVE-2025-3910?

The implications of CVE-2025-3910 include the potential for users to bypass critical security measures like two-factor authentication.

5

Is there a workaround for CVE-2025-3910?

Currently, the recommended approach for CVE-2025-3910 is to update to a patched version of Keycloak rather than using a workaround.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203