PT-2026-33058 · Apache · Apache Airflow
Saurabh Banawar
·
Published
2026-04-15
·
Updated
2026-04-15
·
CVE-2026-25219
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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
Information Disclosure
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Apache Airflow