Skip to main content
VulnerabilityPublished Updated

CVE-2026-40961: Apache Airflow · Authenticated users can bypass the `is_safe_url` check

Affects apache-airflowSource GCVE Database

0
Compare
Authoritative record:CVE-2026-40961· High 7.2

Not known to be exploited · CVSS 7.2 High : upgrade to 3.2.2 soon.

Data as of 3 Nov 2026, 00:29 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.2.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jun 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 2 Nov 2026.

What to do

Upgrade apache-airflow to 3.2.2.

Affected software

ProductAffectedFixed in
PyPIapache-airflowAffected
  • >=3.0.0b3 <3.2.2
Fixed in
  • 3.2.2

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

AI-suggested

Upgrade Apache Airflow to version 3.2.2 or later, where this vulnerability is fixed. As a defense-in-depth measure, deploy Airflow behind a reverse proxy configured to strip off-domain `next=` query parameters before they reach the login endpoint. No other specific mitigations are indicated by the vendor advisory.

Description

Apache Airflow versions from 3.0.0b3 up to but not including 3.2.2 contain a vulnerability in the login redirect route that allows authenticated users to bypass the `is_safe_url` check. This flaw enables redirection from a trusted Airflow domain to an attacker-controlled origin. The issue is fixed in version 3.2.2. Operators are advised to upgrade to 3.2.2 or later. As an additional mitigation, deploying Airflow behind a reverse proxy that removes off-domain `next=` query parameters before they reach the login endpoint can reduce risk.

References

Community reviews

Loading reviews…