# Apache Airflow Providers Edge3 exposes internal API allowing RCE in web server context Advisory record · `GHSA-66h8-3g48-6hx8` - **Identifiers:** `GHSA-66h8-3g48-6hx8` · `CVE-2025-67895` · `PYSEC-2025-87` · `PYSEC-2026-276` - **State:** Confirmed - **Severity:** CVSS 9.8 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-669](https://cwe.mitre.org/data/definitions/669.html) - **Tags:** [CWE-669](https://agentprime.io/advisories/tag/cwe-669.md) - **Published:** 17 Dec 2025 - **Updated:** 26 Oct 2026 - **Reviewed by a person:** No 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. ## Critical Critical, because: - CVSS score 9.8: 9.0 or more. How we decide what’s critical: ## Affected packages - `apache-airflow-providers-edge3` (PyPI): affected `<2.0.0`; fixed in `2.0.0` ## 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 - 9.8 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.012, the 67th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:07 UTC: First seen by agentprime - 31 Oct 2026, 14:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-66h8-3g48-6hx8) ## Sources - [GitHub Advisory Database: GHSA-66h8-3g48-6hx8](https://github.com/advisories/GHSA-66h8-3g48-6hx8) - [OSV: GHSA-66h8-3g48-6hx8](https://osv.dev/vulnerability/GHSA-66h8-3g48-6hx8) - - - - - - - - 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. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .