CVE-2026-76186: 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
This Apache advisory covers CVE-2026-76186. Related products: Apache Airflow Keycloak.
- CVE-2026-76186
Key facts
- Vendor rating
- Critical, CVSS 9.1
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N· base score 9.1, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: none.- Weakness
- CWE-565: Reliance on Cookies without Validation and Integrity Checking in a Security Decision
- EPSS
- 0.81% chance of exploitation in the next 30 days (57th percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: yes. Technical impact: total. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Versions named
- Apache Airflow Keycloak provider before 0.10.0
- Fixed in
- 0.10.0
- Source published
- Source revised
- Listed by VulniPulse
- Record changed
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Related products & platforms
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.
Text from the source record.
- Apache Airflow Keycloak provider before 0.10.0
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-76186
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- 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.
End-of-life dates for Apache Airflow
More Apache Software Foundation advisories
CVE-2026-76187Sep 16, 2026Apache Airflow Keycloak provider: the unauthenticated token endpoint acceptsCVE-2026-96295Nov 20, 2026Apache Texera: Authenticated users can bypass normal controls on the reading and writingCVE-2026-121649Nov 19, 2026Apache Tomcat information disclosureCVE-2026-133325Nov 19, 2026Key exchange without entity authentication vulnerability in Apache TomcatCVE-2026-118436Nov 19, 2026Apache Tomcat denial of serviceCVE-2026-118233Nov 19, 2026Apache Tomcat denial of service
Apache Software Foundation advisories, September 2026All Apache Software Foundation advisories
Get an email when Apache Airflow publishes the next one.
See Apache Airflow's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.