{
  "from_raw": "Rahul Vats <rahulvats@apache.org>",
  "from": "Rahul Vats <ra...@apache.org>",
  "gravatar": "0fbe946dc8945f95479d159e3e3a6c12",
  "to": "an...@apache.org,\n us...@airflow.apache.org",
  "subject": "CVE-2026-82355: Apache Airflow: Session cookie silently overrides explicit Authorization bearer header, enabling session fixation",
  "message-id": "<ad36132d-1e9f-5883-b7b7-9f1fd73284e9@apache.org>",
  "mid": "rwytbrhpysqn8mhx1s72d93tycs40142",
  "permalinks": [
    "rwytbrhpysqn8mhx1s72d93tycs40142",
    "r180b70238329e94365bf41a9b016f6f69db2a67ddc5554843ca60e4a@<announce.apache.org>"
  ],
  "dbid": "d655294901bebf1b6c0a301221d3c2e5a2a29b944a4605a45611a609b4690c41",
  "cc": "us...@airflow.apache.org",
  "epoch": 1789996945,
  "list": "<announce.apache.org>",
  "list_raw": "<announce.apache.org>",
  "date": "2026/09/21 13:22:25",
  "private": false,
  "references": "",
  "in-reply-to": "",
  "body": "Severity: low \n\nAffected versions:\n\n- Apache Airflow 3.3.0 before 3.3.2\n\nDescription:\n\nWhen 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.\n\nCredit:\n\nClaude Security Scans (tool)\nJarek Potiuk (remediation developer)\n\nReferences:\n\nhttps://github.com/apache/airflow/pull/72225\nhttps://github.com/apache/airflow/pull/72723\nhttps://airflow.apache.org/\nhttps://www.cve.org/CVERecord?id=CVE-2026-82355\n\n",
  "body_short": "Severity: low \n\nAffected versions:\n\n- Apache Airflow 3.3.0 before 3.3.2\n\nDescription:\n\nWhen a request to the Airflow core API carries both a session cookie and an explicit `Authorization: Bearer` token",
  "html_source_only": false,
  "attachments": [],
  "forum": "announce@apache.org",
  "size": 4365,
  "id": "rwytbrhpysqn8mhx1s72d93tycs40142"
}