Servers and applications
CVE-2025-66236
Before Airflow 3.2.0, it was unclear that secure Airflow deployments require the Deployment Manager to take appropriate actions and pay attention to security details and security model of Airflow. Some assumptions the Deployment Manager could make were not clear or explicit enough, even though Airflow's intentions and security model of Airflow did not suggest different assumptions. The overall…
- Severity
- High 7.5
- Published
- 13 Apr 2026
- Last changed
- 3 Nov 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.2.0
- Exploit chance
- 0.4% in the next 30 daysHigher than 39% of CVEs. EPSS by FIRST, 18 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N- Sources
- NVD
Description
Before Airflow 3.2.0, it was unclear that secure Airflow deployments require the Deployment Manager to take appropriate actions and pay attention to security details and security model of Airflow. Some assumptions the Deployment Manager could make were not clear or explicit enough, even though Airflow's intentions and security model of Airflow did not suggest different assumptions. The overall security model [1], workload isolation [2], and JWT authentication details [3] are now described in more detail. Users concerned with role isolation and following the Airflow security model of Airflow are advised to upgrade to Airflow 3.2, where several security improvements have been implemented. They should also read and follow the relevant documents to make sure that their deployment is secure enough. It also clarifies that the Deployment Manager is ultimately responsible for securing your Airflow deployment. This had also been communicated via Airflow 3.2.0 Blog announcement [4].
Affected software
| Software | Affected versions |
|---|---|
Apache AirflowServers and applications · cpe:a:apache:airflow |
|
About Apache Airflow
open-source workflow management platform written in Python, where workflows are created via Python scripts
- Weekly downloads (PyPI)
- 1,437,607PyPI Stats, 15 Nov 2026
- Docker Hub pulls
- 1,734,204,390Docker Hub, 15 Nov 2026
- GitHub stars
- 47,481GitHub, 15 Nov 2026
- Forks
- 18,360GitHub, 15 Nov 2026
- Latest release
- 3.4.0GitHub, 15 Nov 2026
- Released
- 6 Nov 2026GitHub
- Developer
- Apache Software FoundationWikidata
- License
- Apache Software License 2.0, Apache LicenseWikidata
- Written in
- PythonWikidata
- First published on GitHub
- 13 Apr 2015GitHub
Website Source code Docker image Package
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 3.4 | 3.4.0 | Yes |
| 3.3 | 3.3.2 | Ended 7 Nov 2026 |
| 3.2 | 3.2.2 | Ended 6 Jul 2026 |
| 3.1 | 3.1.8 | Ended 7 Apr 2026 |
| 3.0 | 3.0.6 | Ended 25 Sept 2025 |
| 2 | 2.11.2 | Ended 22 Apr 2026 |
From endoflife.date.
Vulnerabilities in Apache Airflow
- In our list
- 176
- Published in the last 12 months
- 83
- Critical, last 12 months
- 6
- High, last 12 months
- 30
- Known exploited
- 2
- CVE-2026-40913Apache Airflow: Import Errors API Leaks Unauthorized DAG Stack Traces via Incomplete Per-File RBAC EnforcementHigh 8.2 9 Nov 2026
- CVE-2026-50204Apache Airflow: Audit-log secrets masker redacts by key name only, persisting connection and Variable secrets in cleartextMedium 6.5 9 Nov 2026
- CVE-2026-68982Apache Airflow: CeleryExecutor: forged callback workloads run on Celery workers without workload-token validationCritical 9.8 9 Nov 2026
- CVE-2026-86829Apache Airflow: Deserialization of task-controlled XCom values in the Scheduler during dependency evaluationHigh 8.8 9 Nov 2026
- CVE-2026-82337Apache Airflow: DeadlineAlert fields bypass plugin-registration gate for scheduler-side deserializationHigh 7.3 9 Nov 2026
- CVE-2026-86468Apache Airflow: CLI argv masking misses Variable values and --conn-extra, persisting secrets in audit logsMedium 6.5 9 Nov 2026