Apache Airflow Keycloak provider: Reliance on Cookies without Validation and Integrity Checking
CVE-2026-76186 is a critical-severity reliance on cookies without validation and integrity checking vulnerability in Apache Airflow Keycloak provider from Apache, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 0.10.0 as the first without the flaw, so updating Apache Airflow Keycloak provider to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.81% chance of exploitation within 30 days, higher than 58% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Apache Airflow Keycloak provider to 0.10.0 or a later version.
- Update Apache-airflow-providers-keycloak to 0.10.0 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | Apache Airflow Keycloak provider | before 0.10.0 | 0.10.0 |
| Apache | Apache-airflow-providers-keycloak | before 0.10.0 | 0.10.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CISA (ADP).
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Reliance on Cookies without Validation and Integrity Checking
The product relies on the existence or values of cookies when performing security-critical operations, but it does not properly ensure that the setting is valid for the associated user.
How developers prevent this class of flaw
- Avoid using cookie data for a security-related decision.
- Perform thorough input validation (i.e.: server side validation) on the cookie data if you're going to use it for a security related decision.
- Add integrity checks to detect tampering.
More Reliance on Cookies without Validation and Integrity Checking vulnerabilities (CWE-565)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Apache Airflow Keycloak provider
- 9.8 Critical severity
Recent Reliance on Cookies without Validation and Integrity Checking vulnerabilities
- 9.8 Critical severity
- 8.3 High severity
- 8.1 High severity
- 9.1 Critical severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.