CVE-2026-58065 Apache Software Foundation CVE debrief

Who should care

Defenders responsible for Apache Airflow deployments using the Git DAG bundle or Git provider to clone over SSH with a deploy key should assess exposure and prioritize remediation.

Why it matters

CVE-2026-58065 allows man-in-the-middle attacks due to the Apache Airflow Git provider's default SSH host-key verification setting. Defenders should prioritize upgrading to apache-airflow-providers-git 0.4.1 or later and configuring a known_hosts file to verify host keys. This vulnerability affects deployments using the Git DAG bundle or Git provider to clone over SSH with a deploy key. Evidence from official sources supports these impacts, but further verification is required to determine the full scope of affected versions and deployments.

• Intercepting SSH deploy keys, allowing unauthorized access to Git repositories
• Injecting malicious repository content, potentially leading to downstream vulnerabilities
• Impersonating the Git server, enabling man-in-the-middle attacks
• Compromising the integrity of Git-based workflows and deployments

Technical summary

The Apache Airflow Git provider runs its git-over-SSH operations with StrictHostKeyChecking=no by default, disabling SSH host-key verification. This allows an attacker who can intercept the network path between an Airflow worker and the Git server to impersonate the server, capturing the SSH deploy key or injecting malicious repository content. Deployments using 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.

Defensive priority

Defenders should prioritize upgrading to apache-airflow-providers-git 0.4.1 or later and configuring a known_hosts file to verify host keys.

Recommended defensive actions

• Upgrade to apache-airflow-providers-git 0.4.1 or later
• Configure a known_hosts file to verify host keys
• Review and update SSH deploy key configurations
• Monitor Git repository content for malicious changes
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. Evidence from official sources supports these impacts, but further verification is required to determine the full scope of affected versions and deployments. The official CVE Program record and NVD detail page offer source-provided CVE metadata and vulnerability assessment. However, additional verification tasks are necessary to confirm the extent of affected systems and deployments.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.