Approved changes feed: RSS · Atom

cpe:2.3:a:apache_software_foundation:apache_airflow_providers_edge3:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorApache Software Foundation (f563070d-e18f-561b-b86c-987936937e8a)
ProductApache Airflow Providers Edge3 (d37a2525-be91-5aa2-aa07-79ed2b3e502c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2025-67895 vulnerable 2026-06-08 07:41:20.562895 Apache Airflow Providers Edge3: Edge3 Worker RPC RCE on Airflow 2
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.
Published: 2025-12-17T11:47:42.502Z
Updated: 2025-12-17T19:55:36.494Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.