Git server impersonation via disabled host verification
Published Jul 13, 2026 · Updated Jul 13, 2026
Key-exchange authentication failure in Apache Airflow Git Provider before 0.4.1 allows man-in-the-middle attackers to impersonate Git servers. The Git hook defaults strict_host_key_checking to no and directs known_hosts to /dev/null, causing SSH transport to accept any presented server host key. Reachability requires a network-path position and a deployment that clones through the Git DAG bundle or provider over SSH with a deploy key; the attacker can steal that key or inject repository content.
Summary
What happened
Key-exchange authentication failure in Apache Airflow Git Provider before 0.4.1 allows man-in-the-middle attackers to impersonate Git servers. The Git hook defaults strict_host_key_checking to no and directs known_hosts to /dev/null, causing SSH transport to accept any presented server host key. Reachability requires a network-path position and a deployment that clones through the Git DAG bundle or provider over SSH with a deploy key; the attacker can steal that key or inject repository content.
The record
- CVE
- CVE-2026-58065
- Published
- Jul 13, 2026
- Updated
- Jul 13, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Airflow Git Provider
- Classifications
- CWE-322, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2026CVE publishedPublication date reported by the CVE source.
- Jul 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.4.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo