AI Science Tracker

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

Apache Airflow Keycloak provider · AI involvement attributed to Claude Security Scans

Finding and attribution

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 auth

Product: Apache Airflow Keycloak provider. AI system: Claude Security Scans. Team / organization: apache (CNA); AI attribution as credited in the CVE record.

CVE identifiers: CVE-2026-76186.

AI and human contribution (source account): The CNA record credits 'Claude Security Scans; Jarek Potiuk'. It states the AI attribution as written there and does not describe the model's operation, autonomy or the human validation steps; none is inferred.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The CNA record establishes a coordinated disclosure with the credit above. It does not establish exploitation in the wild or a zero-day incident.

Remediation status: fix documented. CNA record links a fix commit or pull request; no fixed release version is stated in the record. Deployed patch status is not checked.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 16 Sep 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Critical · highest recorded score 9.1. Documented technical effects: Not available.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Documented fix: CNA record links a fix commit or pull request; no fixed release version is stated in the record. Deployed patch status is not checked.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases