CVE-2026-76186

Apache Airflow Keycloak provider: Keycloak token cookies not bound to Airflow session identity

Published Sep 16, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
Apache Airflow Keycloak provider: from Airflow 3.3 the Keycloak auth manager takes a user's identity from the signed Airflow session token but takes the Keycloak access and refresh tokens used for every authorization decision from separate, unauthenticated cookies, and never checks that the two describe the same subject. A user who holds any valid Airflow login of their own, together with another subject's Keycloak access or refresh token obtained out of band, can pair the two: Airflow then authorizes requests with the foreign token's privileges while the session identity, audit log and cache keys continue to name the attacker's own account. The refresh path re-issues an Airflow session token for the original identity carrying the foreign tokens, so the mismatched pairing survives across sessions.

Affects deployments running Airflow 3.3 or later with the Keycloak auth manager. Earlier versions carried the Keycloak tokens inside the signed session token, so the binding existed and was lost when they moved into separate cookies.

Users of apache-airflow-providers-keycloak are recommended to upgrade to version 0.10.0 or later, which binds the cookie-supplied tokens to the session identity.

Analysis

AI-generated

Technical impact

The vulnerability arises because the Airflow Keycloak authenticator separates the signed session token from the Keycloak access and refresh tokens, which are instead stored in separate, unauthenticated cookies. When a user logs in, Airflow takes the session identity from the signed token but uses the tokens from the cookies to make authorization decisions, without verifying that the cookie tokens correspond to the same subject. As a result, an authenticated user who also has a foreign Keycloak access or refresh token can pair their own session with the foreign token. Based on the description, the likely attack vector is manipulating the unauthenticated cookie to supply a foreign Keycloak token, allowing the system to honor the foreign privileges while the audit logs and session name continue to reference the attacker’s account.

Affected Systems

The flaw impacts any Airflow deployment using version 3.3 or newer with the apache-airflow‑providers‑keycloak package configured to use the Keycloak authentication manager. All users of this provider that rely on cookie‑supplied Keycloak tokens are affected. Deployments running Airflow before 3.3 embed the Keycloak tokens inside the signed session token, so these earlier releases are not impacted by this issue.

Risk and Exploitability

With a CVSS score of 9.1, the flaw carries high severity. Although the EPSS score is less than 1 percent, the vulnerability enables a straightforward privilege escalation that does not require special network or privilege exploits. The attacker only needs a valid Airflow login for themselves and an additional Keycloak token for another user, which can be obtained through token leakage or social engineering. The lack of token binding means that the mismatch survives session refreshes, effectively allowing the attacker to perform actions with the foreign user’s permissions while remaining logged in as themselves. The vulnerability is not listed in CISA KEV, but its impact on confidentiality, integrity and availability could be substantial, especially in multi‑tenant environments that rely on Keycloak for role‑based access control.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the apache‑airflow‑providers‑keycloak package to version 0.10.0 or newer, which re‑binds the cookie‑supplied tokens to the Airflow session identity.
  • If an upgrade cannot be performed immediately, force all users to log out, clear all Keycloak cookies, and re‑authenticate to invalidate any foreign tokens that may exist.
  • Consider temporarily disabling the Keycloak authentication manager or reverting to a pre‑3.3 Airflow release that embeds tokens within the signed session.
  • Monitor cookie usage and audit logs for anomalous token activity that may indicate privilege escalation attempts.

Generated by OpenCVE AI on September 18, 2026 at 11:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Apache apache-airflow-providers-keycloak
CPEs cpe:2.3:a:apache:apache-airflow-providers-keycloak:*:*:*:*:*:*:*:*
Vendors & Products Apache apache-airflow-providers-keycloak
Type Values Removed Values Added
First Time appeared Apache
Apache airflow Keycloak Provider
Vendors & Products Apache
Apache airflow Keycloak Provider
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Apache Airflow Keycloak provider: from Airflow 3.3 the Keycloak auth manager takes a user's identity from the signed Airflow session token but takes the Keycloak access and refresh tokens used for every authorization decision from separate, unauthenticated cookies, and never checks that the two describe the same subject. A user who holds any valid Airflow login of their own, together with another subject's Keycloak access or refresh token obtained out of band, can pair the two: Airflow then authorizes requests with the foreign token's privileges while the session identity, audit log and cache keys continue to name the attacker's own account. The refresh path re-issues an Airflow session token for the original identity carrying the foreign tokens, so the mismatched pairing survives across sessions. Affects deployments running Airflow 3.3 or later with the Keycloak auth manager. Earlier versions carried the Keycloak tokens inside the signed session token, so the binding existed and was lost when they moved into separate cookies. Users of apache-airflow-providers-keycloak are recommended to upgrade to version 0.10.0 or later, which binds the cookie-supplied tokens to the session identity.
Title Apache Airflow Keycloak provider: Keycloak token cookies not bound to Airflow session identity
Weaknesses CWE-565
References
Weaknesses
  • CWE-565

    Reliance on Cookies without Validation and Integrity Checking

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Sep 17, 2026, 7:22 PM
Reserved
Aug 19, 2026, 10:41 AM
Status
Analyzed
Published
Sep 16, 2026, 10:16 AM
Modified
Sep 18, 2026, 2:26 PM