- Exploited
- No known exploitation
- Fix
- Fixed in 15.3.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 15.3.1.
Summary
The Apache Airflow Microsoft Azure provider, specifically its S3ToAzureBlobStorageOperator, turns off TLS certificate checks for its connection to Amazon S3 by default, whatever the AWS connection's own settings say. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read it, and alter object keys and copied file contents.
Original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach12/20apache-airflow-providers-microsoft-azure: 124.9K downloads a week
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Impact
- Widely used
apache-airflow-providers-microsoft-azure has 124.9k weekly downloads.Source: pypistats.org
3 packages depend on apache-airflow-providers-microsoft-azure.Source: deps.dev
What to do
Upgrade to a fixed version: 15.3.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129509 (Apache Airflow Microsoft Azure provider: S3ToAzureBlobStorageOperator disables S3 TLS verification by default), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129509 (entry last updated 2026-11-18):
Affected:
- PyPI package apache-airflow-providers-microsoft-azure: from 10.2.0, fixed in 15.3.1
Fixed versions: 15.3.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129509 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129509 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/z6o61d0h81o1f9bgdrn4d9jl24o7shmh
- https://github.com/apache/airflow/pull/76222
- http://www.openwall.com/lists/oss-security/2026/11/17/30
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129509
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129509"}.Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
From 10.2.0 · fixed in 15.3.1
Fixed in 15.3.1 (released Nov 9, 2026, 9 days before disclosure).
The latest release, 15.3.1, is not affected.
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread/z6o61d0h81o1f9bgdrn4d9jl24o7shmh |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129509 |
| Record | NVD · CVE-2026-129509 |
| Write-ups 1Establishes: Technical detail and context. | |
| Link | openwall.com · lists/oss-security/2026/11/17/30 |
| Other links 1 | |
| Patch | GitHub · apache/airflow · Pull request #76222 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129509
Is CVE-2026-129509 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-129509?
apache-airflow-providers-microsoft-azure (PyPI): from 10.2.0 before 15.3.1.Source: cve.now feed data
How do I fix CVE-2026-129509?
Upgrade to a fixed version: 15.3.1.Source: cve.now feed data