CVE-2025-67895
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-17

Last updated on: 2025-12-22

Assigner: Apache Software Foundation

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 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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-17
Last Modified
2025-12-22
Generated
2026-05-07
AI Q&A
2025-12-17
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
apache apache-airflow-providers-edge3 to 2.0.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-669 The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Edge3 provider for Apache Airflow 2, which was development-only and not officially released. If installed and configured, it enabled a non-public API that allowed a DAG author to perform Remote Code Execution (RCE) in the webserver context, which they should not have been able to do. This means an attacker with DAG author permissions could execute arbitrary code on the Airflow webserver.


How can this vulnerability impact me? :

If you installed and configured the Edge3 provider on Airflow 2, an attacker with DAG author permissions could exploit this vulnerability to execute arbitrary code remotely on the Airflow webserver. This could lead to unauthorized control over the server, data compromise, or further attacks within your environment. Users of Airflow 3 or Edge3 provider versions 2.0.0 and above are not affected.


What immediate steps should I take to mitigate this vulnerability?

If you have installed and configured the Edge3 provider on Airflow 2, you should immediately uninstall the Edge3 provider and migrate to Airflow 3. The Edge3 provider versions 2.0.0 and above require Airflow 3 and have removed the vulnerable code that allowed Remote Code Execution in Airflow 2. If you are using Edge3 provider on Airflow 3, you are not affected. [2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart