Is CVE-2026-82355 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-82355 being exploited in the wild.

How severe is CVE-2026-82355?

Medium severity, with a CVSS score of 4.2, published 21 September 2026.

Which products and versions are affected?

Apache Airflow 3.3.0, 3.3.1; apache-airflow (PyPI) ECOSYSTEM:introduced=0,last_affected=3.3.0,last_affected=3.3.1.

Is there a fix for CVE-2026-82355?

A patch was published on 2026-09-08: Fix merged in PR #72225 to apache:main Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-82355 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-82355?

Check whether you run Apache Airflow or apache-airflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-82355: Apache Airflow authentication bypass via session cookie precedence

CVE-2026-82355 · Severity: medium · CVSS 4.2 · Published 2026-09-21

Apache Airflow's core API incorrectly prioritizes session cookies over explicit authentication tokens when both are present in a request, causing the system to authenticate the request under the wrong user identity. An attacker must first place a malicious session cookie into a victim's browser—possible through cross-site scripting or cookie tossing—then make an API request that carries both the attacker's cookie and a legitimate Authorization token. The result is that API calls execute and are audited under the attacker's identity rather than the legitimate user's, leading to misattributed actions and false audit trails.

Technologies: Apache Airflow, apache-airflow (PyPI). Vendors: Apache, PyPI.

Quick answers

Is CVE-2026-82355 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82355 being exploited in the wild.
How severe is CVE-2026-82355?: Medium severity, with a CVSS score of 4.2, published 21 September 2026.
Which products and versions are affected?: Apache Airflow 3.3.0, 3.3.1; apache-airflow (PyPI) ECOSYSTEM:introduced=0,last_affected=3.3.0,last_affected=3.3.1.
Is there a fix for CVE-2026-82355?: A patch was published on 2026-09-08: Fix merged in PR #72225 to apache:main Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-82355 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-82355?: Check whether you run Apache Airflow or apache-airflow (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability stems from incorrect credential resolution logic in Airflow 3.3.0 and 3.3.1, where session cookies are resolved and cached before checking for explicit Bearer tokens, causing the bearer token to be silently ignored. The attack requires pre-existing placement of a valid session cookie in the victim's client—typically via XSS, cookie tossing from a sibling domain, or local access. This results in principal confusion and audit log misattribution; it does not grant direct privilege escalation. The fix (merged in PR #72225) ensures explicit credentials are resolved with priority over session cookies.

Affected products

Apache Airflow 3.3.0, 3.3.1

Identifiers

CVE-2026-82355
PYSEC-2026-3989

Timeline

2026-09-21: disclosed
2026-09-08: patched: Fix merged in PR #72225 to apache:main

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.