Apache Airflow Provider for Databricks: TLS Certificate Verification is Disabled in Databricks Provider K8s Token Exchange

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.8 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-32794: 0.39% estimated exploitation activity in the next 30 days; percentile 33.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Improper Certificate Validation vulnerability in Apache Airflow Provider for Databricks. Provider code did not validate certificates for connections to Databricks back-end which could result in a man-of-a-middle attack that traffic is intercepted and manipulated or credentials exfiltrated w/o notice. This issue affects Apache Airflow Provider for Databricks: from 1.10.0 before 1.12.0. Users are recommended to upgrade to version 1.12.0, which fixes the issue.

Published by the source

31 Mar 2026, 00:31 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:40 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wrpj-755p-x363

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wrpj-755p-x363

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32794

Advisory: Apache Airflow Provider for Databricks: TLS Certificate Verification is Disabled in Databricks Provider K8s Token Exchange
IDs: CVE-2026-32794, GHSA-wrpj-755p-x363
Record: https://patchnext.com/advisories/cve-2026-32794 (revision 2, source checked 26 Oct 2026, 13:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: apache-airflow 1.12.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI apache-airflow: affected >= 1.10.0, < 1.12.0; fixed in 1.12.0

## Suggested inspection (read-only)
- `python -m pip show apache-airflow`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on apache-airflow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-wrpj-755p-x363 (OSV record GHSA-wrpj-755p-x363 lists affected ranges: PyPI apache-airflow >=1.10.0 <1.12.0 (fixed))
- Verified: https://github.com/advisories/GHSA-wrpj-755p-x363 (GitHub-reviewed advisory GHSA-wrpj-755p-x363 lists affected ranges: PyPI apache-airflow >=1.10.0 <1.12.0)

Commands are suggestions: review each one before running it.