Airflow Azure provider skipped S3 TLS checks by default (CVE-2026-129509)
Versions 10.2.0 through 15.3.0 set s3_verify=False even when the AWS connection required verification; 15.3.1 fixes it.
Disabled S3 TLS verification in Airflow Azure provider operator
In Apache Airflow's Microsoft Azure provider 10.2.0 through 15.3.0, S3ToAzureBlobStorageOperator disables TLS certificate verification for Amazon S3 by default, ignoring the AWS connection's verification settings. An attacker on the path between an Airflow worker and S3 can intercept that traffic, read signed requests, and alter listed object keys and copied file contents. Deployments are affected when a DAG uses this operator without setting s3_verify.
What to do: Upgrade apache-airflow-providers-microsoft-azure to 15.3.1 or later so S3 verification follows the AWS connection settings.
| Product | Affected | Fixed in |
|---|---|---|
| apache-airflow-providers-microsoft-azure | 10.2.0 through 15.3.0 | 15.3.1 or later |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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.
Versions 10.2.0 through 15.3.0 set s3_verify=False even when the AWS connection required verification; 15.3.1 fixes it.
Today 2.5K readers · 2.8K views · 144 reads · all time 206K views