endoflife.ai
Apache Airflow EOL Checker

Apache Airflow 3.3 End of Life: Superseded by 3.4 on November 6, 2026

By Scott Bissett  ·  Published: November 7, 2026  ·  Reference guide  ·  Read from the Airflow supported-versions table and release announcement on the day of publication.

Apache Airflow 3.3 stopped receiving fixes on November 6, 2026, the day Airflow 3.4.0 was released. The Airflow project announced 3.4.0 on November 6, 2026. Its supported-versions table tracks support by major version: the 3 line is in Maintenance, and the current minor release of that line is 3.4. Patch releases now come from 3.4, so a deployment that stays on 3.3 gets no further fixes. Airflow 3.3 was first released on July 6, 2026.

The Airflow 3 line itself is supported. The table lists Airflow 3 in Maintenance, with its Limited Maintenance and EOL dates marked TBD. What ends is the 3.3 minor release: staying supported means staying on the newest 3.x minor.
Quick answer: Apache Airflow 3.3 reached end of life (EOL) on November 6, 2026. Apache Airflow 3.4 is supported, with no end-of-life date announced yet. Every Apache Airflow version's release and end-of-support date is on the Apache Airflow lifecycle page.

What the supported-versions table says

Airflow lineStateLimited maintenanceEOL
3 (current minor: 3.4)MaintenanceTBDTBD
2EOLOctober 22, 2025April 22, 2026

The table defines the two states that come after Maintenance: limited support versions "will be supported with security and critical bug fixes only", and EOL versions "will not get any fixes or support". Inside a supported major line, fixes ship on the newest minor release; that is why 3.3 stops at the 3.4.0 release rather than at a date of its own. Every version is on the Apache Airflow page.

Running Apache Airflow past end of life?
Extended support past the official EOL date exists for many products in this position — whether it covers Apache Airflow is exactly what we check. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

Security exposure

Airflow has two entries in CISA's Known Exploited Vulnerabilities catalog, both from 2020 and both about the 1.10 line: CVE-2020-11978 (command injection in an example DAG) and CVE-2020-13927 (the old Experimental API default that allowed unauthenticated requests). Neither is a reason to stay on 3.3. The reason to move is the general one: a 3.x issue found from now on is fixed in 3.4 and later, not in 3.3.

What to do

  1. Find every Airflow 3.3 deployment, including managed environments and container images pinned to a 3.3 tag.
  2. Read the 3.4.0 release notes (linked from the Airflow announcement) for breaking changes and provider requirements before upgrading.
  3. Upgrade to 3.4 and run the database migration (airflow db migrate) as part of the upgrade, testing DAGs in a staging environment first.
  4. Still on Airflow 2? It reached end of life on April 22, 2026; the move to 3.x is a major-version migration with its own upgrade guide.

Frequently Asked Questions

Is Apache Airflow 3.3 end of life?

Airflow 3.3 stopped receiving fixes when Airflow 3.4.0 was released on November 6, 2026. The Airflow project's supported-versions table tracks support by major version: the 3 line is in Maintenance and its current minor release is 3.4, so new fixes ship on 3.4.

Is Airflow 3 still supported?

Yes. The Airflow 3 line is in Maintenance in the project's supported-versions table, with Limited Maintenance and EOL dates still marked TBD. Support continues through the newest 3.x minor release.

When did Airflow 2 reach end of life?

The Airflow supported-versions table lists Airflow 2 as EOL: limited maintenance began October 22, 2025 and end of life was April 22, 2026. EOL versions get no fixes or support.

Related

© 2026 endoflife.ai · How we verify our dates · API · About