AIRFLOW COVERAGE
Airflow 2 is end of life. Your pipelines do not have to move this quarter.
Apache Airflow extended support from OSSeva keeps Airflow 2.x patched after the Airflow project ended it on 22 April 2026: 2.11.2, the last 2.x release, shipped on 14 March 2026. Critical CVEs are fixed within 48 hours and High within 7 days, priced per application. Other versions are assessed case by case through a version coverage check.
| Who it is for | Data platform teams running Airflow 2.x in production that cannot move to Airflow 3 yet |
|---|---|
| What you get | Signed builds with security fixes backported to Airflow 2, and no change to your DAGs, connections or metadata schema. Assure adds a DAG-by-DAG Airflow 3 assessment. |
| How it is priced | Per application. Ask for a quote. |
| What happens next | You send your work email, we confirm your Airflow version, executor and providers, and you get a coverage plan. |
Reply within 1 business day · No commitment · or book a 15-minute call
Last reviewed
Trusted globally by enterprises





Airflow support status, read on 19 November 2026
The Airflow project tracks Airflow 3 as one line in Maintenance with no end date announced. endoflife.date derives a date for each 3.x minor, which is when the next minor was released.
| Line | First release | Upstream status | Latest release |
|---|---|---|---|
| Airflow 2 | 17 Dec 2020 | End of life, 22 Apr 2026 | 2.11.2 (14 Mar 2026) |
| Airflow 3 line | 22 Apr 2025 | Maintenance, end date TBD | 3.4.0 (6 Nov 2026) |
| 3.3 | 6 Jul 2026 | Ended 7 Nov 2026 (endoflife.date) | 3.3.2 (17 Sep 2026) |
| 3.2 | 7 Apr 2026 | Ended 6 Jul 2026 (endoflife.date) | 3.2.2 (29 May 2026) |
Sources: airflow.apache.org supported-versions page and endoflife.date/api/apache-airflow.json, read on 19 November 2026.
Why now
Airflow 2 reached end of life on 22 April 2026
The Airflow supported-versions page lists Airflow 2 as EOL with a termination date of 22 April 2026, after limited maintenance from 22 October 2025. The last release was 2.11.2 on 14 March 2026.
Airflow 3 changes how tasks reach the metadata database
The Airflow 3 upgrade guide says tasks can no longer read the metadata database directly and must use the Task Execution API. Custom tasks that query it need rework, so the move is a code audit, not a version bump.
SubDAGs, SLAs and the Sequential Executor are removed
Per the same guide, Airflow 3 removes SubDAGs, SLAs, the Sequential Executor and the /api/v1 REST API. Estates that use them need rework before they can leave Airflow 2.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 2.x(Community EOL 22 Apr 2026; last release 2.11.2) | EOL | Clean |
| 3.x(Maintained upstream. Assessed case by case.) | Current | Clean |
Running a Apache Airflow version or build not listed here?
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Security patches for Airflow 2.x after end of life.
- Backported security fixes for Apache Airflow 2.x
- Critical CVEs fixed within 48 hours, High within 7 days
- Signed artifacts (GPG + Sigstore)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus compliance documentation and migration planning.
- Everything in Patch
- SOC 2 / HIPAA attestation package
- Airflow 3 migration assessment of your DAGs
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.
- Everything in Assure
- 24/7 scheduler and worker monitoring
- 15-minute P1 incident response SLA
- Named senior engineer on your account
All tiers priced per cluster/application — not per core.
Which Airflow versions does OSSeva patch?
Airflow 2.x after end of life. Other versions are assessed case by case through a version coverage check.
Is Apache Airflow 2 end of life?
Yes. The Airflow supported-versions page gives Airflow 2 a termination date of 22 April 2026, and 2.11.2 was its last release.
How fast are Airflow vulnerabilities patched?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.
How is OSSeva Airflow support priced?
It is priced per application. Request a quote and a senior engineer replies within 1 business day.
Get a quote
Ready to get Apache Airflow patched and supported?
Tell us your Apache Airflow versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?