Apache Airflow 2 · Version Status
Apache Airflow 2 End of Life Date
Apache Airflow 2 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Apache Airflow 2 is past end of life. This version no longer receives security patches. 199 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 22, 2026
199 days past EOL
Latest Release
2.11.2
Standard release
Release Date
Dec 17, 2020
Apache Airflow 2 series
Where these dates come from
End of lifeApr 22, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of active supportOct 22, 2025endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseDec 17, 2020endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Apache Airflow 2 was released on December 17, 2020 and support ended on April 22, 2026 — a supported lifespan of 5 years and 4 months, longer than the 8 months median for Apache Airflow releases. Its latest release on record is 2.11.2, published March 14, 2026 — 39 days before support ended. It has been past its end-of-life date for 7 months. 2 newer Apache Airflow releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Apache Airflow 2 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All Apache Airflow Versions
| Version | Latest | EOL Date | Status |
|---|
| 1.7 |
1.7.1.2 |
Mar 19, 2017 |
EOL |
| 1.8 |
1.8.2 |
Jan 3, 2018 |
EOL |
| 1.9 |
1.9.0 |
Aug 27, 2018 |
EOL |
| 1.10 |
1.10.15 |
Jun 17, 2021 |
EOL |
| → 2 |
2.11.2 |
Apr 22, 2026 |
EOL |
| 3.0 |
3.0.6 |
Sep 25, 2025 |
EOL |
| 3.1 |
3.1.8 |
Apr 7, 2026 |
EOL |
| 3.2 |
3.2.2 |
Jul 6, 2026 |
EOL |
What does Apache Airflow 2 end of life mean?
When Apache Airflow 2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Apache Airflow 2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Apache Airflow 3.4 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Apache Airflow 2 reach end of life?
Apache Airflow 2 reached end of life on April 22, 2026. This version is no longer receiving security patches.
Is Apache Airflow 2 still supported?
No. Apache Airflow 2 reached end of life on April 22, 2026 and is no longer receiving security patches.
What should I upgrade to from Apache Airflow 2?
The recommended upgrade from Apache Airflow 2 is
Apache Airflow 3.4 — the latest actively supported version. Check the
Apache Airflow full timeline for all supported versions.
What are the security risks of running Apache Airflow 2 past EOL?
Since Apache Airflow 2 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Apache Airflow should migrate immediately or implement compensating controls.