CVE-2026-81914

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.3Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Apache Airflow's Google provider built Google Drive search expressions by interpolating file and folder names directly into single-quoted string literals, without escaping the quote character that delimits them. A name containing an apostrophe therefore terminated the literal early and appended clauses of the attacker's choosing to the query.

The names are frequently not written by the Dag author. In a wildcard gcs_to_gdrive transfer they come from the source bucket listing, so anyone able to create objects in that bucket controls them — typically an external data producer or an ingest-only service account, a different trust principal from the Dag author. An injected clause can broaden the match and so steer which file or folder the hook resolves: an upload can be directed into a folder the attacker named, and, because downloads select the most recently modified match, a download can return a file they placed rather than the one the Dag asked for.

Affects deployments passing externally-sourced names to the Google Drive hook, including wildcard gcs_to_gdrive transfers from buckets writable by less-trusted principals. Users are advised to upgrade to apache-airflow-providers-google 22.6.0 or later, which escapes quote and backslash characters in every value interpolated into a Drive query.

CVSS v3
4.3
EG Score
4.3MEDIUMhigh confidence
EG Risk
34
EG Risk 34/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 29, 2026

Advisory Details (2)

Auto-updated Sep 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Escape values interpolated into Google Drive q= queries

Fix merged in apache/airflow PR #72166 on 2026-09-20 — awaiting tagged release

https://github.com/apache/airflow/pull/72166

Vendor Advisories for CVE-2026-81914(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 04:29 UTCEG score recompute
  2. 2026-10-05 04:29 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 03:13 UTCEG score recompute
  5. 2026-10-04 03:13 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-03 01:58 UTCEG score recompute
  8. 2026-10-03 01:58 UTCGHSA enrichment
  9. 2026-10-02 17:57 UTCEPSS rescore
  10. 2026-10-02 00:43 UTCEG score recompute
  11. 2026-10-02 00:43 UTCGHSA enrichment
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-09-30 23:26 UTCEG score recompute
  14. 2026-09-30 23:26 UTCGHSA enrichment
  15. 2026-09-30 15:04 UTCEPSS rescore
  16. 2026-09-29 22:10 UTCEG score recompute
  17. 2026-09-29 22:10 UTCGHSA enrichment
  18. 2026-09-29 20:30 UTCEG score recompute▲ 4.30
  19. 2026-09-29 20:29 UTCGHSA enrichment
  20. 2026-09-29 20:29 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
  21. 2026-09-29 16:05 UTCEG score recompute
  22. 2026-09-29 16:05 UTCGHSA enrichment
  23. 2026-09-29 12:33 UTCGHSA enrichment
  24. 2026-09-29 12:33 UTCNVD update
  25. 2026-09-29 11:23 UTCMITRE cvelistV5
Show 3 more
  1. 2026-09-29 10:28 UTCNVD update
  2. 2026-09-29 10:01 UTCEG score recompute
  3. 2026-09-29 09:58 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81914?
CVE-2026-81914 is a medium vulnerability published on September 29, 2026. Apache Airflow's Google provider built Google Drive search expressions by interpolating file and folder names directly into single-quoted string literals, without escaping the quote character that delimits them. A name containing an apostrophe therefore terminated the literal early and appended…
When was CVE-2026-81914 disclosed?
CVE-2026-81914 was first published on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81914 actively exploited?
CVE-2026-81914 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81914?
CVE-2026-81914 has a CVSS v3.1 base score of 4.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-81914?
An upstream fix for CVE-2026-81914 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-81914 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81914

Explore →

Is Your Infrastructure Affected by CVE-2026-81914?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.