CVE-2026-25219

published 15 Apr 2026 · updated 3 Nov 2026

Apache Airflow: Sensitive Azure Service Bus connection string (and possibly other providers) exposed to users with view access

6.5MediumCVSS 6.5EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Airflow 3.2.0, 3.0.0 and 3.1.8.

The `access_key` and `connection_string` connection properties were not marked as sensitive names in secrets masker. This means that user with read permission could see the values in Connection UI, as well as when Connection was accidentaly logged to logs, those values could be seen in the logs. Azure Service Bus used those properties to store sensitive values. Possibly other providers could be also affected if they used the same fields to store sensitive data. If you used Azure Service Bus connection with those values set or if you have other connections with those values storing sensitve values, you should upgrade Airflow to 3.1.8

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
ApacheAirflow<3.2.03.2.0
Apache Software Foundation<3.0.0, >=3.0.0 <3.1.83.0.0, 3.1.8

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Airflow, strongest first

10.0CriticalCISA KEVPublic exploit

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-25219 severity on Zeptric[![CVE-2026-25219](https://zeptric.io/badge/cve/CVE-2026-25219.svg)](https://zeptric.io/cve/CVE-2026-25219)