cve.bz

CVE-2026-25219 apache airflow

6.5 mediumEPSS 0.6%Fix available

Medium (6.5) in apache airflow. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in apache-airflow 3.1.8.

On this 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

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-25219 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-25219?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-25219?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-25219 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-25219

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-25219](https://cve.bz/cve/badge/CVE-2026-25219.svg)](https://cve.bz/cve/CVE-2026-25219)

HTML:

<a href="https://cve.bz/cve/CVE-2026-25219"><img src="https://cve.bz/cve/badge/CVE-2026-25219.svg" alt="CVE-2026-25219"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Airflowbefore 3.0.0
Apache Software Foundation Apache Airflowfrom 3.0.0 before 3.1.8

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-4g48-54q2-fg7qPyPIapache-airflow<3.1.83.1.8
PYSEC-2026-2344PyPIapache-airflow<3.1.83.1.8

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON