Skip to main content
VulnerabilityPublished

CVE-2026-113508: Apache Airflow · DEPRECATED: Insufficient Session Expiration

Affects Apache AirflowSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to 3.4.0 soon.

Data as of 9 Nov 2026, 10:33 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 3.4.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade Apache Airflow and apache-airflow-core to 3.4.0.

Affected software

ProductAffectedFixed in
Apache Airflowapache-airflow-coreAffected
  • <3.4.0
Fixed in
  • 3.4.0
PyPIapache-airflow-corepkg:pypi/apache-airflow-coreOther threatsAffected
  • <3.4.0
Fixed in
  • 3.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to Apache Airflow version 3.4.0 or later, where this issue is fixed. No other mitigations are indicated. Since this is a software vulnerability with an official fix, applying the update is the recommended remediation.

Description

Apache Airflow's logout endpoint attempted to revoke the presented token on the server, but any failure during revocation was silently ignored and logout still reported success. When the auth manager redirects logout to an external logout URL (for example the FAB or Keycloak auth managers), server-side revocation is the only thing that invalidates the Airflow token; it failed on database errors and, reliably, for tokens from an external issuer accepted via `[api_auth] trusted_jwks_url` whose token identifier is longer than 32 characters. Anyone holding a copy of a user's token from before logout could keep using it against the Airflow API until it expired. Users are advised to upgrade to apache-airflow 3.4.0 or later.

References

Community reviews

Loading reviews…