- Exploited
- No known exploitation
- Fix
- Fixed in 3.4.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.4.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache Airflow reports a successful logout without revoking the user's token on the server, so an attacker who holds a copy of that token from before logout can keep using it against the Airflow API until it expires. Revocation fails 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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach12/20apache-airflow-core: 647K downloads a week
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Impact
- Widely used
apache-airflow-core has 647k weekly downloads.Source: pypistats.org
473 packages depend on apache-airflow-core.Source: deps.dev
What to do
Upgrade to a fixed version: 3.4.0.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
fixed in 3.4.0
Fixed in 3.4.0 (released Nov 6, 2026, 3 days before disclosure).
The latest release, 3.4.0, is not affected.
Evidence 4
- Advisory
- Patch
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-113508
Is CVE-2026-113508 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-113508?
apache-airflow-core (PyPI): before 3.4.0.Source: cve.now feed data
How do I fix CVE-2026-113508?
Upgrade to a fixed version: 3.4.0.Source: cve.now feed data