CVE-2025-65995: Apache Airflow - Disclosure of Secrets to UI via kwargs

airflow Updated 24 Feb 2026

Summary

24/02/2026
Yes i
Medium
Not published

CVE-2025-65995: Apache Airflow: Disclosure of secrets to UI via kwargs. Affects airflow across 2 version ranges.

< 2.11.1 >= 3.0.0, < 3.1.4

Fixed in 2.11.1 or 3.1.4, depending on the release line you run. How to fix ↓

Also tracked for

The same CVE-2025-65995 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Airflow is an open-source platform designed to programmatically author, schedule, and monitor workflows. It allows users to define complex data pipelines using Directed Acyclic Graphs (DAGs). Airflow's extensibility and user-friendly interface make it a popular choice among data engineers and scientists. However, like any software, it is susceptible to vulnerabilities that can compromise sensitive information.

Vulnerability Detail

The vulnerability arises when a Directed Acyclic Graph (DAG) fails during parsing, leading to the inclusion of full keyword arguments (kwargs) in the error-reporting UI. If these kwargs contain sensitive information, such as secrets or credentials, they could be exposed to authenticated users who have permission to view the affected DAG. This could lead to unauthorized access to sensitive data, potentially compromising the security of the entire system.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.11.1 2.11.1
  • >= 3.0.0, < 3.1.4 3.1.4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, users can avoid passing sensitive information in the kwargs of operators until they are able to upgrade to the patched versions. Additionally, reviewing and limiting user permissions for viewing DAGs can help mitigate the risk of exposure.

Conclusion

The CVE-2025-65995 vulnerability in Apache Airflow poses a significant risk by potentially exposing sensitive information through the UI. Users are strongly advised to upgrade to the latest patched versions to mitigate this risk. Implementing best practices for handling sensitive data and user permissions can further enhance security.

See every vulnerability recorded for airflow →

Share this vulnerability

FAQ

CVE-2025-65995 is a vulnerability in Apache Airflow that allows for the disclosure of sensitive information through the UI when a DAG fails during parsing.

Any user of Apache Airflow versions prior to 2.11.1 and 3.1.4 who has permission to view DAGs may be affected by this vulnerability.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If immediate upgrading is not possible, consider reviewing and limiting user permissions for viewing DAGs and avoid passing sensitive information in kwargs.

More information can be found in the official Apache Airflow documentation and the vulnerability database at https://github.com/bitnami/vulndb.

Related vulnerabilities

Recent vulnerabilities recorded for airflow.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.11.1 2.11.1
  • >= 3.0.0, < 3.1.4 3.1.4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback