CVE-2026-129509: Apache Airflow Microsoft Azure provider · Improper Certificate Validation
Affects Apache Airflow Microsoft Azure providerSource CVE Database V5
Not known to be exploited : upgrade to 15.3.1 soon.
Data as of 18 Nov 2026, 10:34 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 15.3.1
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Apache Airflow Microsoft Azure provider and apache-airflow-providers-microsoft-azure to 15.3.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Airflow Microsoft Azure providerapache-airflow-providers-microsoft-azure | Affected
| Fixed in
|
PyPIapache-airflow-providers-microsoft-azurepkg:pypi/apache-airflow-providers-microsoft-azureOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to apache-airflow-providers-microsoft-azure version 15.3.1 or later, where the S3ToAzureBlobStorageOperator uses the AWS connection's TLS certificate verification settings by default. This update restores proper certificate validation and mitigates the risk of man-in-the-middle attacks. Users should ensure that the `s3_verify` parameter is not set to false or omitted in vulnerable versions.
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.