ZDF
Sign inSign up

Vulnerabilities

Security incident · CVE-2026-82355

When a request to the Airflow core API carries both a session cookie and an explicit token, Airflow resolves the caller from the cookie and ignores the bearer token, i…

Published Sep 21, 2026 · catalog updated Sep 25, 2026 · the affected product

Last checked Nov 2, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-82355. EPSS is 0.73%. Act only if a listed version of the affected product is installed.

Gaps on this record

  • No plain product name is stored. The page cannot tell you which product to check.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium4.2
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.73%
Remediation
Advisory link
Affected products
cpe apache/airflow

When a request to the Airflow core API carries both a session cookie and an explicit 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe apache/airflow3.3.0
  • cpe apache/airflow3.3.1

How to fix CVE-2026-82355

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    Seen in 3.3.0 · 1 other packages on the advisory

  • Advisory

    Open the inventory_high record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-82355. EPSS is 0.73%. Act only if a listed version of the affected product is installed.

Which versions are affected?

Compare what you have installed with 3.3.0, 3.3.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-384. EPSS 0.73%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Apache Airflow security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Sep 21, 2026 · Monitored products — high

    Detected

    When a request to the Airflow core API carries both a session cookie and an explicit 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 an

  2. Sep 25, 2026 · Monitored products — high

    Updated

    When a request to the Airflow core API carries both a session cookie and an explicit 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 an

Sources

  • Monitored products — highVendor advisoryCVE-2026-82355

    When a request to the Airflow core API carries both a session cookie and an explicit 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 an

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 2, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Monitored products — highNov 2, 2026