Is apache-airflow-providers-edge3 1.3 vulnerable?

PyPI · 2 releases from 1.3.0 to 1.3.1 · latest apache-airflow-providers-edge3 is 5.1.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. apache-airflow-providers-edge3 1.3.1, the last 1.3 release, is affected by 1 known security advisory (1 critical), including CVE-2025-67895. Upgrade to 2.0.0 or later to fix all of them.

Upgrade with:pip install 'apache-airflow-providers-edge3>=2.0.0'

Is your project on an affected apache-airflow-providers-edge3?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting apache-airflow-providers-edge3 1.3.1

  • CriticalCVE-2025-67895GHSA-66h8-3g48-6hx817 Dec 2025

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

    Affected
    <2.0.0
    Fixed in
    2.0.0

Every apache-airflow-providers-edge3 1.3.x release

Affected: 1.3.0 to 1.3.1. Latest apache-airflow-providers-edge3: 5.1.1.

VersionKnown advisories
apache-airflow-providers-edge3 1.3.1CVE-2025-67895
apache-airflow-providers-edge3 1.3.0CVE-2025-67895

Which of your client projects are still on apache-airflow-providers-edge3 1.3?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact apache-airflow-providers-edge3 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other apache-airflow-providers-edge3 versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.