Apache Airflow Providers Edge3Web server / proxy · Apache
CVE-2025-67895
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEdge3 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Edge3 provider for Apache Airflow 2 enabled an undocumented internal API that allowed Dag Authors to execute arbitrary code in the webserver context, achieving unauthenticated Remote Code Execution. This development-only API was never intended for production use in Airflow 2.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Apache Airflow Providers Edge3Web server / proxy
< 2.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Edge3 provider is installedRun 'airflow providers list' or 'pip list | grep -i edge3' to check if the Edge3 provider package is present in your Airflow environmentAffected if The Edge3 provider package appears in the provider list or pip output
-
Check installed Edge3 provider versionRun 'airflow providers get apache-airflow-providers-edge3' or check pip output for the exact version number of the edge3 providerAffected if The version number is lower than 2.0.0 (e.g., 1.x.x series)
-
Confirm Airflow version is 2.xRun 'airflow version' to determine if you are running Airflow 2 (vulnerable) versus Airflow 3 (not affected by this specific CVE)Affected if Airflow version reports as 2.x (for example, 2.3.0, 2.7.0, etc.)
-
Check if Edge3 provider is enabledInspect your airflow.cfg or Airflow metadata database for the 'edge3' provider in the 'enabled' column of the 'providers' table, or check if any Edge3-specific connections existAffected if The Edge3 provider shows as enabled or active in your configuration
You are affected if the Edge3 provider is installed with a version lower than 2.0.0 on an Airflow 2.x deployment and the provider is enabled in your configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.0
Uninstall the Edge3 provider from Airflow 2 and migrate to Airflow 3 with Edge3 provider version 2.0.0 or higher, or simply remove the provider if the functionality is not required.
Apache Airflow 3.x with Apache Airflow Providers Edge3 >= 2.0.0
- Identify if Apache Airflow Providers Edge3 is installed on Airflow 2 by checking your installed packages
- If Edge3 provider is installed on Airflow 2, plan migration to Airflow 3 (upgrade Airflow core first)
- Upgrade to Apache Airflow 3.x
- Upgrade Apache Airflow Providers Edge3 to version 2.0.0 or later (pip install apache-airflow-providers-edge3>=2.0.0)
- Verify the upgrade completed successfully and the vulnerable API is no longer present
- If migration to Airflow 3 is not possible immediately, uninstall the Edge3 provider from Airflow 2 (pip uninstall apache-airflow-providers-edge3) until migration can be completed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Apache Airflow Providers Edge3
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67895 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data