Quick answers
- Is CVE-2026-81914 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81914 being exploited in the wild.
- How severe is CVE-2026-81914?
- Low severity, with a CVSS score of 3.1, published 29 September 2026.
- Which products and versions are affected?
- Apache Airflow Google provider before 22.6.0; apache-airflow-providers-google (PyPI) ECOSYSTEM:introduced=0,fixed=22.6.0.
- Is there a fix for CVE-2026-81914?
- Yes. apache-airflow-providers-google (PyPI): upgrade to 22.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81914 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-81914?
- Check whether you run Apache Airflow Google provider 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.6.0 or later
pip install "apache-airflow-providers-google>=22.6.0"
Technical details
The vulnerability is a string injection flaw in the Google Drive query builder where file and folder names from external sources (such as GCS bucket listings) are interpolated directly into single-quoted query strings without escaping quote characters. An attacker can inject additional query clauses by using an apostrophe in a file/folder name to break out of the string literal. This affects wildcard gcs_to_gdrive transfers where bucket contents are controlled by lower-privileged principals, enabling file steering attacks.
Affected products
- Apache Airflow Google provider before 22.6.0
Identifiers
- CVE-2026-81914
- PYSEC-2026-4187
Timeline
- 2026-09-29: disclosed
- 2026-09-20: patched: Fix merged in PR #72166, available in apache-airflow-providers-google 22.6.0