No verified lifecycle record
Apache Airflow 3.4 end-of-life and support dates
No end-of-support date is published for Apache Airflow 3.4. No verified lifecycle record for this exact scope.
Scope: software releaseListed under Apache AirflowAs of 2026-11-10
Lifecycle timeline
- 2026-11-07 — Release date · General availability
Why this status?
Only “Release date” (general-availability, 2026-11-07, confirmed) is published; the vendor has not published any end-of-support milestone for this exact scope.
Evidence
- Apache Airflow version lifecycle Official · checked 2026-11-10
- endoflife.date product data independent-open · checked 2026-11-10
Related
- All Apache Airflow lifecycle dates· 10 tracked releases
- Apache Airflow security advisories· 114 tracked
- CVE-2026-68982: Apache Airflow's CeleryExecutor ran callback workloads (`ExecuteCallback`, used for deadline-alert callbacks) without validating the workload's authentication token
- CVE-2026-76185: Apache Airflow's Task SDK secret cache built its keys from the team name and secret id with unescaped `_` delimiters, so different (team, secret id) pairs could collide
- CVE-2026-86829: Apache Airflow's scheduler fully deserializes XCom values written by task code while evaluating task dependencies
- CVE-2026-107474: Apache Airflow: Connections API: apprise connection "config" extra returned in cleartext
- CVE-2026-111421: Apache Airflow's Task Execution API stored XCom values written by a task without the reserved-key check applied elsewhere, so a Dag author's task could write an XCom that, when a user later viewed it through the API with deserialization enabled, made the API server instantiate classes from the `airflow.*` namespace with arguments the Dag author chose
- CVE email alerts for Apache
Status is calculated from the published milestones. When a vendor does not publish a date, this page says so and does not estimate one.