Advisory

GHSA-66h8-3g48-6hx8

Also known as: CVE-2025-67895, PYSEC-2025-87, PYSEC-2026-276

Summary

Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context

Details

Edge3 Worker RPC RCE on Airflow 2.

This issue affects Apache Airflow Providers Edge3: before 2.0.0 - and only if projects 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 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.

If 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.

If projects used Edge Provider in Airflow 3, you they are not affected.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2025-12-17 12:30 UTC
Modified
2026-10-26 21:30 UTC

Affected packages and fixes

apache-airflow-providers-edge3

PyPI · All systems

Affected

  • introduced 0, fixed 2.0.0 (ecosystem)

Fixed versions

2.0.0

Fix

  • Fixed version 2.0.0
    pip install --upgrade apache-airflow-providers-edge3==2.0.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences