Advisory record · GHSA-66h8-3g48-6hx8

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

CVSS 9.8 CriticalCriticalEPSS 0.012 · 67th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 17 Dec 2025, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
apache-airflow-providers-edge3PyPI<2.0.02.0.0
Identifiers
GHSA-66h8-3g48-6hx8 · CVE-2025-67895 · PYSEC-2025-87 · PYSEC-2026-276
Weakness (CWE)
CWE-669
Published
17 Dec 2025
Updated
26 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The apache-airflow-providers-edge3 package is vulnerable before version 2.0.0 when it was installed and configured on Airflow 2; the source notes this provider was development-only on Airflow 2. An attacker who can author DAGs can use an internal API that the provider enabled to run code in the webserver context, which DAG authors should not be able to do. The fix is to uninstall the provider on Airflow 2 and migrate to Airflow 3, since version 2.0.0 and later require Airflow 3 and remove the affected code; projects using Edge3 on Airflow 3 are not affected.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.012, the 67th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.