The Apache Airflow Git provider runs its git-over-SSH operations with `StrictHostKeyChecking=no` by default, disabling SSH host-key verification. An attacker who can intercept the network path between an Airflow worker and the Git server can impersonate the server (man-in-the-middle), capturing the SSH deploy key or injecting malicious repository content. Deployments that use the Git DAG bundle or Git provider to clone over SSH with a deploy key are affected. The fix changes the default to verify host keys; upgrade to apache-airflow-providers-git `0.4.1` or later and configure a `known_hosts` file.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/apache/airflow/pull/69103 Issue Tracking, Patch
- https://lists.apache.org/thread/fjmclngfksz2kp7llpcjxzdz568h0zhc Mailing List, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.1 · apacheNVD modified 2026-10-24 22:10
Affected (CPE criteria) 1
cpe:2.3:a:apache:apache-airflow-providers-git:*:*:*:*:*:*:*:*
References 3
- https://github.com/apache/airflow/pull/69103 Issue Tracking, Patch
- https://lists.apache.org/thread/fjmclngfksz2kp7llpcjxzdz568h0zhc Mailing List, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/07/13/3 Mailing List, Third Party Advisory