WhatBrokeToday
GTA 6FAQ
Apache

Apache Airflow Microsoft Azure Provider TLS Verification Disabled for S3

high

Is it fixed? Not yet.

Ongoing since Nov 18, 10:16 UTC. First reported Nov 18, 10:16 UTC.

What happened

In Apache Airflow Microsoft Azure provider versions 10.2.0 through 15.3.0, the S3ToAzureBlobStorageOperator disables TLS certificate verification for Amazon S3 connections by default. This exposes deployments to potential network interception and traffic alteration attacks between Airflow workers and S3.

What caused it?

The S3ToAzureBlobStorageOperator explicitly disabled TLS certificate verification for its connection to Amazon S3 by default (s3_verify=False), ignoring the AWS connection's own verification settings.

Source: tenable.com

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Official fix

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on security advisory

    Apache Airflow Microsoft Azure provider 10.2.0: CVE-2026-129509 (High)

    Source

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    Apache Airflow Microsoft Azure provider 10.2.0: CVE-2026-129509 (High)(opens security advisory in a new tab)

    High severity. 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…

    by Tenable 0upvotes 0comments

FAQ

What happened in the Apache issue?

In Apache Airflow Microsoft Azure provider versions 10.2.0 through 15.3.0, the S3ToAzureBlobStorageOperator disables TLS certificate verification for Amazon S3 connections by default. This exposes deployments to potential network interception and traffic alteration attacks between Airflow workers and S3.

What is affected by the Apache issue?

Apache (versions: 10.2.0 through 15.3.0).

When did the Apache issue start and end?

It started Nov 18, 10:16 UTC and is still ongoing (18 h 27 min so far). This page updates as it develops.

How do I get alerts for Apache?

Subscribe to the Apache RSS feed for every new Apache incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Apache is down. Apache feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.