Quick answers
- Is CVE-2026-45361 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45361 being exploited in the wild.
- How severe is CVE-2026-45361?
- High severity, with a CVSS score of 8.1, published 25 May 2026.
- Which products and versions are affected?
- apache-airflow-providers-google (PyPI) ECOSYSTEM:introduced=0,fixed=22.0.0.
- Is there a fix for CVE-2026-45361?
- Yes. apache-airflow-providers-google (PyPI): upgrade to 22.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45361 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45361?
- Check whether you run Apache Software Foundation Airflow Google Provider, Apache Software Foundation Airflow Providers Google or apache-airflow-providers-google (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- apache-airflow-providers-google (PyPI): upgrade to 22.0.0 or later
pip install "apache-airflow-providers-google>=22.0.0"
Technical details
The `ComputeEngineSSHHook` in the Apache Airflow Google provider (apache-airflow-providers-google) was found to hard-code the `paramiko.AutoAddPolicy` for SSH connections. This configuration disables strict host-key verification (CWE-322), meaning the client automatically trusts any host key presented by a remote server. An in-path network attacker can exploit this to perform a Man-in-the-Middle (MitM) attack, intercepting or modifying the SSH traffic between the Airflow worker and the Google Compute Engine VM. The vulnerability is addressed in version 22.0.0 by introducing a `host_key_policy` parameter that allows users to configure strict verification.
Affected products
- Apache Software Foundation apache-airflow-providers-google < 22.0.0
Identifiers
- CVE-2026-45361
- GHSA-g9v5-gjwf-9rwx
- PYSEC-2026-166
Timeline
- 2026-05-24: disclosed: Initial disclosure on oss-security mailing list
- 2026-05-25: advisory: NVD publication date
- 2026-05-26: advisory: GitHub Advisory published
- 2026-06-30: patched: GitHub Advisory reviewed and updated with patch information
References
- https://github.com/apache/airflow/pull/66746
- https://lists.apache.org/thread/3lpj7ppwxp7jtp81rnxk75xvln7qd7h2
- http://www.openwall.com/lists/oss-security/2026/05/24/9
- https://github.com/apache/airflow/commit/120dbed3462cedcb980aac022c587ba434249eb1
- https://github.com/pypa/advisory-database/tree/main/vulns/apache-airflow-providers-google/PYSEC-2026-166.yaml