CVE-2026-25219
mediumpriority · track · 0EPSS 0.006 · 46 %ileDEEUUSEPSS · scored 2026-10-27
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
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (6)
Products and version ranges known to be affected.
advisories (4)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-1153Apache Airflow: Schwachstelle ermöglicht Offenlegung von InformationenDeutsch2026-04-15csaf · cert_bundDE
Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Apache Airflow ausnutzen, um Informationen offenzulegen.
- GHSA-4g48-54q2-fg7qApache Airlfow: Sensitive Azure Service Bus connection string (and possibly other providers) exposed to users with view access2026-04-15ghsa · osvUS
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 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.
- BIT-airflow-2026-25219Apache Airflow: Sensitive Azure Service Bus connection string (and possibly other providers) exposed to users with view access2026-04-18vendor · osvUS
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
- PYSEC-2026-2344Apache Airlfow: Sensitive Azure Service Bus connection string (and possibly other providers) exposed to users with view access2026-07-13vendor · osvUS
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 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.
also known as (7)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (9)
External citations — patches, advisories, analysis.
- https://lists.apache.org/thread/t4dlmqkn0njz4chk3g7mdgzb96y4ttqhPatchcnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2026-25219cnnvd
- https://github.com/apache/airflow/pull/61580enisa_euvd
- https://github.com/apache/airflow/pull/61582enisa_euvd
- https://lists.apache.org/thread/t4dlmqkn0njz4chk3g7mdgzb96y4ttqhenisa_euvd
- http://www.openwall.com/lists/oss-security/2026/04/15/3Mailing ListThird Party Advisorynvd
- https://github.com/apache/airflow/pull/61580Issue Trackingnvd
- https://github.com/apache/airflow/pull/61582Issue Trackingnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan