← Back
CVE-2026-45361
high
CVSS 8.1
Vulnerability in apache-airflow-providers-google (CVE-2026-45361)
Summary
vulnerability in apache-airflow-providers-google (CVE-2026-45361). Successful exploitation can lead to full system takeover. Exploitable via ``ComputeEngineSSHHook``. Mitigation: upgrade to `22.0.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-45361** has been found in apache-airflow-providers-google.
Attackers can target a specific entry point like ``ComputeEngineSSHHook`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade apache-airflow-providers-google to **22.0.0** or later.
If unsure, ask your IT team or search "apache-airflow-providers-google CVE-2026-45361" on the vendor's site.
CVE-2026-45361 (apache-airflow-providers-google) — CWE-322 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `ComputeEngineSSHHook`
Patched: `22.0.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-322) exists in apache-airflow-providers-google. Attackers reach the vulnerable code path via ``ComputeEngineSSHHook`` without authentication.
📍 Affected scope
apache-airflow-providers-google — . Attack surface: `ComputeEngineSSHHook`.
🔥 Severity
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **22.0.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'apache-airflow-providers-google' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'apache-airflow-providers-google' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `apache-airflow-providers-google` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade apache-airflow-providers-google to 22.0.0ステージング環境で 22.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
apache-airflow-providers-google
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.0.0"}]}]
pip
apache-airflow-providers-google
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"22.0.0"}]}]
References
- web https://nvd.nist.gov/vuln/detail/CVE-2026-45361
- web https://github.com/apache/airflow/pull/66746
- web https://lists.apache.org/thread/3lpj7ppwxp7jtp81rnxk75xvln7qd7h2
- web http://www.openwall.com/lists/oss-security/2026/05/24/9
- web https://github.com/advisories/GHSA-g9v5-gjwf-9rwx
- web [email protected]
- web https://github.com/apache/airflow/commit/120dbed3462cedcb980aac022c587ba434249eb1
- web https://github.com/pypa/advisory-database/tree/main/vulns/apache-airflow-providers-google/PYSEC-2026-166.yaml