CVE-2026-25219: Apache Airflow: Sensitive Azure Service Bus connection string (and possibly other providers) exposed to users with view access
The accesskey and connectionstring 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
Other sources
The accesskey and connectionstring 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 accidently 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 senesitve values, you should upgrade Airflow to 3.1.8.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25219?
CVE-2026-25219 is considered a medium severity vulnerability due to the exposure of sensitive connection details.
How do I fix CVE-2026-25219?
To fix CVE-2026-25219, update Apache Airflow to version 3.2.0 or later where the connection properties are properly masked.
Who is affected by CVE-2026-25219?
CVE-2026-25219 affects Apache Airflow versions prior to 3.2.0 with users having read access to connection properties.
What are the risks associated with CVE-2026-25219?
The risks associated with CVE-2026-25219 include potential data breaches as sensitive Azure Service Bus connection strings may be exposed to unauthorized users.
Is there a workaround for CVE-2026-25219?
A possible workaround for CVE-2026-25219 is to restrict user permissions to prevent read access to sensitive connection properties until a proper update can be performed.