Cross-Site Request Forgery (CSRF) in apache-airflow-providers-keycloak (CVE-2026-40948)
Summary
Vulnerability in apache-airflow-providers-keycloak (CVE-2026-40948). Risk of unauthorized operations or information disclosure. Exploitable via state. Mitigation: upgrade to 0.7.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-40948 has been found in apache-airflow-providers-keycloak.
Attackers can target a specific entry point like state over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade apache-airflow-providers-keycloak to 0.7.0 or later.
If unsure, ask your IT team or search "apache-airflow-providers-keycloak CVE-2026-40948" on the vendor's site.
CVE-2026-40948 (apache-airflow-providers-keycloak) — CWE-352 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: state
Patched: 0.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in apache-airflow-providers-keycloak. Attackers reach the vulnerable code path via state without authentication.
Check the vendor advisory for the affected versions of apache-airflow-providers-keycloak. Attack surface: state.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.7.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'apache-airflow-providers-keycloak' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'apache-airflow-providers-keycloak' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
apache-airflow-providers-keycloakを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade apache-airflow-providers-keycloak to 0.7.0ステージング環境で 0.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory lists.apache.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web openwall.com
- web pypi.python.org