GPU VulnDB

Database/Control plane, storage & DevOps

Airflow Azure provider: S3ToAzureBlobStorageOperator disables TLS verification to S3 by default

CVSS 7.5CVE-2026-129509Control plane, storage & DevOpscurated

Impact

In apache-airflow-providers-microsoft-azure 10.2.0 through 15.3.0, S3ToAzureBlobStorageOperator connects to Amazon S3 with certificate verification off (s3_verify=False) and ignores the AWS connection's own verification settings. An attacker on the network path between an Airflow worker and S3 can intercept the traffic, read the signed requests, and change both the listed object keys and the contents of the copied files. On pipelines that move datasets, checkpoints or model artifacts from S3 into Azure Blob, the result is silently tampered training or serving inputs.

Who can reach it

Network attacker positioned between an Airflow worker and the S3 endpoint. No authentication needed. Only affects Dags that use S3ToAzureBlobStorageOperator without setting s3_verify.

What to do

Upgrade apache-airflow-providers-microsoft-azure to 15.3.1 or later, which uses the AWS connection's verification settings by default, and restart the Airflow workers and scheduler so they load the new provider. Until then, set s3_verify explicitly on every use of the operator.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.