CVE-2026-82355: Apache Airflow: Session cookie silently overrides explicit Authorization bearer header, enabling session fixation
This Apache advisory covers CVE-2026-82355 in Apache Airflow.
- CVE-2026-82355
Key facts
- Vendor rating
- Medium, CVSS 4.2
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N· base score 4.2, scored by CISA-ADPAttack vector: network. Attack complexity: high. Privileges required: none. User interaction: required. Scope: unchanged. Confidentiality impact: low. Integrity impact: low. Availability impact: none.- Weakness
- CWE-384: Session Fixation
- EPSS
- 0.73% chance of exploitation in the next 30 days (55th percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
- CISA KEV
- Not listed (catalogue checked )
- Affected
- Apache Airflow 3.3.0 before 3.3.2
- Fixed in
- 3.3.2
- Source published
- Source revised
- Listed by VulniPulse
- Record changed
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
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.
Only 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.
Exploiting 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.
Users 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.
Text from the source record.
- Apache Airflow 3.3.0 before 3.3.2
Official advisory · high-confidence parse· fetched ·verify at source
How to fix CVE-2026-82355
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- Users 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.
Support dates for the fixed release lines
- Apache Airflow 3.3: support ended
More Apache Software Foundation advisories
CVE-2026-40913Nov 9, 2026Apache Airflow: Import Errors API Leaks Unauthorized DAG Stack TracesCVE-2026-50204Nov 9, 2026Apache Airflow: Audit-log secrets masker redacts by key name only, persisting connectionCVE-2026-68982Nov 9, 2026Apache Airflow: CeleryExecutor: forged callback workloads run on Celery workersCVE-2026-86829Nov 9, 2026Apache Airflow: Deserialization of task-controlled XCom values in the SchedulerCVE-2026-82337Nov 9, 2026Apache Airflow: DeadlineAlert fields bypass plugin-registration gate for scheduler-sideCVE-2026-86468Nov 9, 2026Apache Airflow: CLI argv masking misses Variable values and --conn-extra, persisting
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.