CVE-2026-25219
The `access_key` and `connection_string` connection properties were …
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
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/apache/airflow/pull/61580
- github.com/apache/airflow/pull/61582
- lists.apache.org/thread/t4dlmqkn0njz4chk3g7mdgzb96y4ttqh
- www.openwall.com/lists/oss-security/2026/04/15/3
- nvd.nist.gov/vuln/detail/CVE-2026-25219
- github.com/advisories/GHSA-4g48-54q2-fg7q
- nvd.nist.gov/vuln/detail/CVE-2026-25219
- cve.org/CVERecord?id=CVE-2026-25219
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.