CVE-2026-25219 json
Apache Airflow: Sensitive Azure Service Bus connection string (and possibly other providers) exposed to users with view access
published 2026-04-15 6 mo ago modified 2026-11-03 6 d ago also BIT-airflow-2026-25219 , EUVD-2026-22921 , GHSA-4g48-54q2-fg7q , PYSEC-2026-2344
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- pypi apache-airflow 3.1.8
- bitnami airflow 3.1.8
- Apache Software Foundation Apache Airflow 3.0.0, 3.1.8
- github.com/apache/airflow#61580 pull request
- github.com/apache/airflow#61582 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | apache-airflow | <3.1.8 |
3.1.8 |
| bitnami | airflow | <3.1.8 |
3.1.8 |
Affected products
- Apache Software Foundation Apache Airflow
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/apache/airflow/pull/61580
patch, web, issue-tracking, report
-
github.com
/apache/airflow/pull/61582
patch, web, issue-tracking, report
-
lists.apache.org
/thread/t4dlmqkn0njz4chk3g7mdgzb96y4ttqh
vendor-advisory, web, mailing-list, advisory
-
openwall.com
/lists/oss-security/2026/04/15/3
web, mailing-list, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-25219
advisory, web
-
github.com
/apache/airflow
package
-
pypi.org
/project/apache-airflow
package
-
github.com
/advisories/GHSA-4g48-54q2-fg7q
advisory
Sources
- CVE List CVE-2026-25219
- GitHub Advisory GHSA-4g48-54q2-fg7q
- NVD CVE-2026-25219
- OSV BIT-airflow-2026-25219
- OSV PYSEC-2026-2344
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.