CVE-2026-40948: Apache Airflow Providers Keycloak: OAuth Login CSRF — Missing State Parameter in Keycloak Auth Manager

Published Apr 17, 2026
·
Updated

The Keycloak authentication manager in apache-airflow-providers-keycloak did not generate or validate the OAuth 2.0 state parameter on the login / login-callback flow, and did not use PKCE. An attacker with a Keycloak account in the same realm could deliver a crafted callback URL to a victim's browser and cause the victim to be logged into the attacker's Airflow session (login-CSRF / session fixation), where any credentials the victim subsequently stored in Airflow Connections would be harvestable by the attacker. Users are advised to upgrade apache-airflow-providers-keycloak to 0.7.0 or later.

Affected Software

3 affected componentsFixes available
pypi/apache-airflow-providers-keycloak<0.7.0
pip/apache-airflow-providers-keycloak>=0.0.1<0.7.0
0.7.0
Apache apache-airflow-providers-keycloak>=0.0.1<0.7.0

Event History

Apr 18, 2026
CVE Published
via MITRE·01:22 PM
Data Sourced
via MITRE·01:22 PM
DescriptionWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
RemedyAffected Software
Advisory Published
via GitHub·03:34 PM
Data Sourced
via GitHub·03:34 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-40948?

CVE-2026-40948 is a high-severity vulnerability due to the lack of validation on the OAuth 2.0 state parameter which may lead to CSRF attacks.

2

How do I fix CVE-2026-40948?

To fix CVE-2026-40948, upgrade the `apache-airflow-providers-keycloak` package to version 0.7.0 or higher.

3

What is the impact of CVE-2026-40948?

The impact of CVE-2026-40948 includes the potential for attackers to exploit CSRF vulnerabilities during the OAuth 2.0 authentication process.

4

Which versions of software are affected by CVE-2026-40948?

CVE-2026-40948 affects all versions of `apache-airflow-providers-keycloak` below 0.7.0.

5

Is there a mitigation for CVE-2026-40948 without upgrading?

There is no effective mitigation for CVE-2026-40948 other than upgrading to the fixed version.

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