CVE-2025-65995: Apache Airflow Exposes Sensitive kwargs in Error Reporting

apache-airflow Updated 25 Feb 2026

Summary

21/02/2026
Yes i
Moderate
6.5

CVE-2025-65995: Apache Airflow error reporting may expose full kwargs. Affects apache-airflow across 2 version ranges.

< 2.11.1 >= 3.0.0b1, < 3.1.5rc1

Fixed in 2.11.1 or 3.1.5rc1, 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 workflows as Directed Acyclic Graphs (DAGs) and provides a rich user interface to manage and visualize these workflows. However, due to its extensive use of parameters (kwargs) in operators, it can inadvertently expose sensitive information if not properly managed.

Vulnerability Detail

The vulnerability arises when a Directed Acyclic Graph (DAG) fails during parsing. In such cases, Apache Airflow's error reporting mechanism in the user interface may display the complete kwargs passed to the operators. If these kwargs contain sensitive information, such as secrets or credentials, they can be exposed to authenticated users who have permission to view that specific DAG. This could lead to unauthorized access to sensitive data, making it a significant security concern.

How To Fix

Latest published version: 3.3.2 as of 22 Oct 2026

pip install --upgrade "apache-airflow==3.3.2"

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

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

  • < 2.11.1 2.11.1
    pip install --upgrade "apache-airflow==2.11.1"
  • >= 3.0.0b1, < 3.1.5rc1 3.1.5rc1
    pip install --upgrade "apache-airflow==3.1.5rc1"

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 measure, users can avoid including sensitive information in the kwargs passed to operators until they can upgrade to the patched versions. Additionally, consider restricting access to the Airflow UI to limit exposure to authenticated users.

Conclusion

In summary, CVE-2025-65995 is a moderate severity vulnerability in Apache Airflow that can expose sensitive information through error reporting. Users are strongly advised to upgrade to the latest patched versions to mitigate this risk and ensure the security of their workflows.

See every vulnerability recorded for apache-airflow →

Share this vulnerability

FAQ

CVE-2025-65995 is a vulnerability in Apache Airflow that may expose sensitive kwargs in error reporting when a DAG fails during parsing.

If you are using versions prior to 2.11.1 or 3.1.5rc1, your installation is vulnerable to this issue.

Kwargs are keyword arguments that allow users to pass additional parameters to operators in Apache Airflow workflows.

The vulnerability has a CVSS score of 6.5, indicating a moderate severity level, which means it could lead to the exposure of sensitive information.

Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

Related vulnerabilities

Recent vulnerabilities recorded for apache-airflow.

How To Fix

Latest published version: 3.3.2 as of 22 Oct 2026

pip install --upgrade "apache-airflow==3.3.2"

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

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

  • < 2.11.1 2.11.1
    pip install --upgrade "apache-airflow==2.11.1"
  • >= 3.0.0b1, < 3.1.5rc1 3.1.5rc1
    pip install --upgrade "apache-airflow==3.1.5rc1"

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