CVE-2025-67895
Published: 17 December 2025
Description
Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if you installed and configured it on Airflow 2. The Edge3 provider support in Airflow 2 has been always development-only and…
more
not officially released, however if you 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 you installed and configured Edge3 provider for Airflow 2, you should uninstall it and migrate to Airflow 3. The new Edge3 provider versions (>=2.0.0) has 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 you used Edge Provider in Airflow 3, you are not affected.
Mitigating Controls (NIST 800-53 r5)AI
Directly mitigates the RCE vulnerability by requiring timely flaw remediation through updating to Edge3 provider >=2.0.0 or uninstalling from Airflow 2 as per vendor guidance.
Prevents exposure to the RCE-prone non-public API by prohibiting unnecessary development-only functionality such as the Edge3 provider on Airflow 2.
Prohibits the use of unsupported system components like the development-only Edge3 provider for Airflow 2, avoiding installation of the vulnerable software.
Security SummaryAI
CVE-2025-67895 is a remote code execution (RCE) vulnerability in the Edge3 Worker RPC component of Apache Airflow Providers Edge3 versions before 2.0.0. It affects installations where the Edge3 provider has been explicitly installed and configured on Airflow 2. The Edge3 provider support for Airflow 2 was development-only and not officially released; however, configuring it implicitly enabled a non-public API originally used for testing the provider during development.
A DAG author can exploit this non-public API to perform remote code execution in the context of the Airflow webserver, which DAG authors are not supposed to be able to do. The vulnerability is rated with a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating remote network access with low attack complexity, no required privileges or user interaction, and high impacts on confidentiality, integrity, and availability. It is associated with CWE-669.
Apache Airflow advisories recommend uninstalling the Edge3 provider from Airflow 2 and migrating to Airflow 3. Edge3 provider versions 2.0.0 and later set Airflow 3 as the minimum required version and remove the RCE-prone code from Airflow 2 support, making it impossible to use on Airflow 2. Users running the Edge3 provider on Airflow 3 are not affected. Further details are provided in the GitHub pull request at https://github.com/apache/airflow/pull/59143, the Apache mailing list thread at https://lists.apache.org/thread/hhnmmzkj5qx5gbk6pdkh8tcsx5oj1nqs, and the OSS-Security announcement at http://www.openwall.com/lists/oss-security/2025/12/16/3.
Details
- CWE(s)
Affected Products
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Unauthenticated remote code execution vulnerability in a public-facing web application (Apache Airflow webserver component), directly enabling T1190: Exploit Public-Facing Application.