CVE-2025-67895: Apache airflow providers edge3 Remote Code Execution Vulnerability
CRITICALCVE-2025-67895 is a CRITICAL (CVSS 9.8) remote code execution vulnerability (CWE-669: Incorrect Resource Transfer Between Spheres) affecting Apache airflow providers edge3 libraries in the PyPI ecosystem. The issue involves apache airflow providers edge3 exposes internal api allowing rce in web server context. Remediation is available by upgrading affected packages to version 2.0.0.
CVE-2025-67895 at a Glance
Security Impact
CVSS: 9.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2025-67895
To remediate this vulnerability, upgrade all affected Apache airflow providers edge3 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install apache-airflow-providers-edge3>=2.0.0Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show apache-airflow-providers-edge3How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2025-67895, inspect your installed packages using pip:
pip show apache-airflow-providers-edge3Analyze the terminal output to locate any version of Apache airflow providers edge3 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.0), your application is affected.
Note: The pip show apache-airflow-providers-edge3 command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-669: Incorrect Resource Transfer Between Spheres, where 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. In Apache airflow providers edge3, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-67895 Affected Apache airflow providers edge3 Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
apache-airflow-providers-edge3
|
PyPI |
< 2.0.0
|
2.0.0
|
References
Frequently Asked Questions
What is CVE-2025-67895?
Which Apache airflow providers edge3 versions are affected?
What version fixes CVE-2025-67895?
Is apache-airflow-providers-edge3 affected?
What is the CVSS score of CVE-2025-67895?
What CWE is associated with CVE-2025-67895?
How can I check PyPI dependencies for CVE-2025-67895?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-66h8-3g48-6hx8",
"modified" : "2026-06-05T14:18:05Z",
"published" : "2025-12-17T12:30:12Z",
"aliases" : [ "CVE-2025-67895" ],
"summary" : "Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context",
"details" : "Edge3 Worker RPC RCE on Airflow 2.\n\nThis issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects installed and configured it on Airflow 2.\n\nThe 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.\n\nIf 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.\n\nIf projects used Edge Provider in Airflow 3, you they are not affected.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "apache-airflow-providers-edge3"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.0.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-67895"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/airflow/pull/59143"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/airflow"
}, {
"type" : "WEB",
"url" : "https://github.com/pypa/advisory-database/tree/main/vulns/apache-airflow/PYSEC-2025-87.yaml"
}, {
"type" : "WEB",
"url" : "https://lists.apache.org/thread/hhnmmzkj5qx5gbk6pdkh8tcsx5oj1nqs"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2025/12/16/3"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-669" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2025-12-17T22:18:51Z",
"nvd_published_at" : "2025-12-17T12:15:46Z"
}
}