CVE-2026-129509

Apache Airflow Microsoft Azure provider: S3ToAzureBlobStorageOperator disables S3 TLS verification by default

Published Nov 18, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, `S3ToAzureBlobStorageOperator` turned off TLS certificate verification for its connection to Amazon S3 by default (`s3_verify=False`), whatever the AWS connection's own verification settings were. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read the signed requests and alter the listed object keys and the copied file contents. Deployments are affected when a Dag uses `S3ToAzureBlobStorageOperator` without setting `s3_verify`. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 15.3.1 or later, which uses the AWS connection's verification settings by default.

Analysis

AI-generated

Technical impact

Apache Airflow’s Microsoft Azure provider enabled TLS verification disabled by default in the S3ToAzureBlobStorageOperator, which means traffic to Amazon S3 is sent without certificate validation. This omission represents a CWE‑295 weakness that allows an attacker positioned on the network path between an Airflow worker and S3 to intercept traffic, read signed requests, and alter object keys or file contents. The likely attack vector is inferred from the description, as the CVE notes that a network attacker could intercept traffic between the Airflow worker and S3.

Affected Systems

Vulnerable versions of the Apache Airflow Microsoft Azure provider are 10.2.0 through 15.3.0. Users who employ the S3ToAzureBlobStorageOperator without explicitly setting s3_verify to True are impacted.

Risk and Exploitability

The CVSS score is not provided in the current data, and the EPSS score is unavailable, so the likelihood of exploitation is uncertain. The vulnerability is not listed in the CISA KEV catalog. Because the attack requires only network-level access between the Airflow worker and S3, an adversary with that position could exploit the missing TLS validation to compromise confidentiality and integrity of data being transferred. The price to remediate is minimal through an upgrade or configuration change, yet the potential impact is significant if left unpatched.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade apache‑airflow‑providers‑microsoft‑azure to version 15.3.1 or later, which restores default TLS verification.
  • If an upgrade is not yet possible, explicitly configure the operator by setting s3_verify=True in the DAG or Airflow configuration.
  • Contain the Airflow worker network to a trusted segment and enforce TLS inspection or passthrough to prevent attackers from being able to intercept S3 traffic.

Generated by OpenCVE AI on November 19, 2026 at 04:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Apache
Apache airflow Microsoft Azure Provider
Vendors & Products Apache
Apache airflow Microsoft Azure Provider
Type Values Removed Values Added
Description In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, `S3ToAzureBlobStorageOperator` turned off TLS certificate verification for its connection to Amazon S3 by default (`s3_verify=False`), whatever the AWS connection's own verification settings were. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read the signed requests and alter the listed object keys and the copied file contents. Deployments are affected when a Dag uses `S3ToAzureBlobStorageOperator` without setting `s3_verify`. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 15.3.1 or later, which uses the AWS connection's verification settings by default.
Title Apache Airflow Microsoft Azure provider: S3ToAzureBlobStorageOperator disables S3 TLS verification by default
Weaknesses CWE-295
References
Weaknesses
  • CWE-295

    Improper Certificate Validation

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 18, 2026, 10:11 AM
Reserved
Nov 15, 2026, 8:20 PM
Status
Received
Published
Nov 18, 2026, 10:16 AM
Modified
Nov 18, 2026, 11:17 AM