CVE-2026-25219
Apache Airflow vulnerability analysis and mitigation

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


SourceNVD

Related Apache Airflow vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-33858HIGH8.8
  • Apache AirflowApache Airflow
  • airflow
NoYesApr 13, 2026
CVE-2025-54550HIGH8.1
  • Apache AirflowApache Airflow
  • apache-airflow
NoYesApr 15, 2026
CVE-2026-31987HIGH7.5
  • Apache AirflowApache Airflow
  • airflow-3
NoYesApr 16, 2026
CVE-2025-66236HIGH7.5
  • Apache AirflowApache Airflow
  • airflow-3
NoYesApr 13, 2026
CVE-2026-25219MEDIUM6.5
  • Apache AirflowApache Airflow
  • airflow-3
NoYesApr 15, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management