GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow Git provider: SSH host-key verification disabled by default when cloning DAG bundles

CVSS 8.1CVE-2026-58065Control plane, storage & DevOpscurated

Impact

The Git provider runs its git-over-SSH operations with StrictHostKeyChecking=no, so an Airflow worker will accept any host key presented for the Git server. An attacker on the network path between the worker and the Git server can impersonate the server, capture the SSH deploy key, and serve modified repository content. Since the Git DAG bundle is how Airflow workers obtain the code they execute, injected repository content becomes arbitrary code running on the scheduler and worker pods - the same pods that hold pipeline credentials and, in ML fleets, submit and control GPU jobs. The stolen deploy key also gives persistent access to the repository itself.

Who can reach it

Network, no authentication - requires a machine-in-the-middle position between Airflow workers and the Git server (a shared or untrusted network segment, DNS or routing control). Affects deployments that clone over SSH with a deploy key using the Git DAG bundle or Git provider.

What to do

Upgrade apache-airflow-providers-git to 0.4.1 or later, which verifies host keys by default, and supply a known_hosts file for the Git server - the upgrade alone does nothing without that file. A provider package upgrade plus a restart of schedulers and workers; no node reboot. Treat any deploy key that was in use as potentially exposed and rotate it.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.