CVE-2025-67895
Apache-Airflow-Providers-Edge3 ≤ 2.0.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-67895 is a critical-severity Incorrect Resource Transfer Between Spheres (CWE-669) vulnerability in Apache Apache-Airflow-Providers-Edge3. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Escape to Host (T1611); ranked in the top 45% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-203888
Vulnerability Data
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved information flow authorizations between system components and connected systems, directly stopping improper resource transfers across spheres.
Prevents unintended information leakage through shared system resources when crossing sphere boundaries.
Monitors and controls communications at external and key internal boundaries to block unauthorized transfers between trust domains.
Enforces logical access authorizations that limit resource transfers to only approved sphere crossings.
Separates user functionality from system management functions to avoid improper resource or behavior transfer between privilege spheres.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Least-privilege authorization policies directly constrain resource transfers across security domains.
Protecting data-in-transit can limit exposure during inter-sphere transfers but does not address control-flow or authorization errors.
Logical segmentation and access controls reduce unintended cross-sphere resource movement.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Environment separation limits unintended resource leakage between spheres.
Information-transfer rules can prevent improper resource hand-off between spheres.
Access-control policies limit unintended control over transferred resources.
Managing access rights reduces risk of unauthorized resource transfer.
Network-security controls can block improper cross-sphere transfers.
Network segregation directly limits unintended resource movement between spheres.