---
title: "CVE-2025-67895: Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context"
url: https://erroneo.us/security/cve/CVE-2025-67895/
description: "CVE-2025-67895 (apache-airflow-providers-edge3 (PyPI)): Edge3 Worker RPC RCE on Airflow 2. This issue affects Apache Airflow Providers Edge3: before 2.0.0 …"
type: vulnerability-record
section: "Security Digest"
date_published: 2025-12-17
date_modified: 2026-06-05
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2025-67895"
kev: false
cvss: 9.8
epss: 0.00999
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2025-67895: Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 1.0% , percentile 62: FIRST’s model estimates a 1.0% chance of exploitation activity in the next 30 days, higher than 62% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes apache-airflow-providers-edge3 (PyPI) < 2.0.0, fixed in 2.0.0 . Check your lockfile, including transitive dependencies.

## What it is

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.

## Affected packages

- PyPI `apache-airflow-providers-edge3` < 2.0.0 → fixed: 2.0.0

## Affected products (CVE record)

- Apache Software Foundation Apache Airflow Providers Edge3: < 2.0.0

## Severity

- CISA-ADP CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`
- GitHub CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 1.00% probability of exploitation activity in the next 30 days; percentile 62.

## Sources

- [github.com](https://github.com/apache/airflow/pull/59143)
- [lists.apache.org](https://lists.apache.org/thread/hhnmmzkj5qx5gbk6pdkh8tcsx5oj1nqs)
- [GitHub Advisory GHSA-66h8-3g48-6hx8](https://github.com/advisories/GHSA-66h8-3g48-6hx8)
- [CVE.org record CVE-2025-67895](https://www.cve.org/CVERecord?id=CVE-2025-67895)
- [NVD entry CVE-2025-67895](https://nvd.nist.gov/vuln/detail/CVE-2025-67895)
- [openwall.com](http://www.openwall.com/lists/oss-security/2025/12/16/3)
- [github.com](https://github.com/pypa/advisory-database/tree/main/vulns/apache-airflow/PYSEC-2025-87.yaml)

---
Source page: https://erroneo.us/security/cve/CVE-2025-67895/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt