Live › vulnerability › CVE-2025-67895
Go to dashboardThe Edge3 provider for Apache Airflow 2 enabled an internal, non-public API that let a DAG author execute code in the webserver context. An attacker with DAG authoring rights can run arbitrary code on the Airflow webserver.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 21:21 UTC, 1h before NVD. All times on this page are UTC.
Only projects that installed and configured the Edge3 provider on Airflow 2 are exposed, since that setup implicitly enabled the internal test API. Projects running Edge3 on Airflow 3 are not affected, and projects that never installed Edge3 can skip it. The exposure also requires that someone able to author DAGs is not fully trusted.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| apache-airflow-providers-edge3 | pypi | < 2.0.0 | 2.0.0 |
| apache apache-airflow-providers-edge3 | vendor | < 2.0.0 | 2.0.0 |
pip show apache-airflow-providers-edge3 to see the installed provider version, and airflow version to see whether the host runs Airflow 2 or 3apache-airflow-providers-edge3 to 2.0.0 or later, which requires Airflow 3Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Edge3 Worker RPC RCE on Airflow 2.
This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2.
The Edge3 provider support in Airflow 2 has been always development-only and not officially released, however if projects installed and configured Edge3 provider in Airflow 2, it implicitly enabled non-public (normally) API which was used to test Edge Provider in Airflow 2 during the development. This API allowed Dag author to perform Remote Code Execution in the webserver context, which Dag Author was not supposed to be able to do.
If projects installed and configured Edge3 provider for Airflow 2, they should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has a minimum version of Airflow set to 3 and the RCE-prone Airflow 2 code is removed, so it should no longer be possible to use the Edge3 provider 2.0.0+ on Airflow 2.
If projects used Edge Provider in Airflow 3, you they are not affected.
This page as .md · .json · in your agent: get_signal("CVE-2025-67895")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.