{"schema_version": "1.6.1", "id": "CVE-2026-82355", "summary": "Session cookie silently overrides explicit Authorization bearer header, enabling session fixation", "details": "When a request to the Airflow core API carries both a session cookie and an explicit `Authorization: Bearer` token, Airflow resolves the caller from the cookie and ignores the bearer token, inverting the intended precedence of bearer over cookie. The request then executes -- and is recorded in the audit log -- as the cookie's principal rather than the identity the client explicitly presented.\n\nOnly Apache Airflow 3.3.0 and 3.3.1 are affected. Earlier releases do not contain the code path that caches the cookie-derived user, and are not vulnerable.\n\nExploiting this requires an attacker to first place a valid session cookie of their own into the victim's browser or client: for example by cookie tossing from a sibling subdomain, through cross-site scripting in a separate application sharing a parent domain, or via a shared workstation. Deployments that host the Airflow UI on a domain shared with other applications are therefore the most exposed; a deployment on a dedicated domain with no co-hosted applications is not reachable this way. The consequence is principal confusion and misattributed audit records rather than a direct privilege escalation.\n\nUsers of 3.3.0 or 3.3.1 should upgrade to Apache Airflow 3.3.2 or later, which resolves the caller from the explicitly supplied credential whenever one is present.", "affected": [{"ranges": [{"type": "SEMVER", "events": [{"introduced": "3.3.0"}, {"fixed": "3.3.2"}]}]}], "references": [{"type": "WEB", "url": "https://github.com/apache/airflow/pull/72225"}, {"type": "WEB", "url": "https://github.com/apache/airflow/pull/72723"}, {"type": "WEB", "url": "https://lists.apache.org/thread/3p7zpdvv40tn01m0xk5mt2rxg88mw8w1"}]}