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

> Authenticated users can view sensitive secrets in UI tracebacks when DAG parsing fails, requiring an upgrade to Apache Airflow.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Feb 2026
- **Updated:** 8 Mar 2026
- **Also known as:** BIT-airflow-2025-65995, ECHO-c463-1548-b100, GHSA-gfw7-2v73-69wg, MINI-2xqq-86w9-gm35, MINI-44h7-r32v-94v2, PYSEC-2026-2348

## What is CVE-2025-65995?

CVE-2025-65995 is a medium-severity vulnerability in Apache Airflow, published on 21 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

When a DAG failed during parsing, Airflow’s error-reporting in the UI could include the full kwargs passed to the operators. If those kwargs contained sensitive values (such as secrets), they might be exposed in the UI tracebacks to authenticated users who had permission to view that DAG. 

The issue has been fixed in Airflow 3.1.4 and 2.11.1, and users are strongly advised to upgrade to prevent potential disclosure of sensitive information.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2025-65995?

6 open source packages ship an affected version, including apache-airflow and airflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache-airflow` | PyPI | All versions | 2.11.1, 3.1.5rc1 |
| `apache-airflow` | PyPI | All versions | 2.11.1 |
| `apache-airflow` | PyPI | All versions | 2.11.1 |
| `apache-airflow` | PyPI | From 3.0.0b1 | 3.1.5rc1 |
| `apache-airflow` | PyPI | From 3.0.0b1 | 3.1.5rc1 |
| `airflow` | Bitnami | All versions | 2.11.1, 3.1.4 |

Products: Apache Airflow.

## How do I fix CVE-2025-65995?

Upgrade apache-airflow to a fixed version for your release line: 2.11.1 or 3.1.5rc1.

## Is CVE-2025-65995 being exploited?

There is no known exploitation of CVE-2025-65995 in the wild and no public exploit code.

## Other vulnerabilities in Apache Airflow

- [CVE-2020-13927](https://insights.sbomify.com/CVE-2020-13927/): Apache Airflow's Experimental API Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-11978](https://insights.sbomify.com/CVE-2020-11978/): Apache Airflow Command Injection (high 8.8, exploited in the wild)
- [CVE-2026-33264](https://insights.sbomify.com/CVE-2026-33264/): Apache Airflow: DAG author RCE on webserver via unrestricted import_string() in BaseSerialization.deserialize() (critical 9.8)
- [CVE-2023-25754](https://insights.sbomify.com/CVE-2023-25754/): Apache Airflow: Privilege escalation using airflow logs (critical 9.8)
- [CVE-2023-22884](https://insights.sbomify.com/CVE-2023-22884/): Apache Airflow, Apache Airflow MySQL Provider: Arbitrary file read via MySQL provider in Apache Airflow (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65995 and fix it if it is affected.

What it is: CVE-2025-65995 is a medium-severity vulnerability in Apache Airflow, published on 21 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-65995 in the wild and no public exploit code.

Affected packages and fixed versions:
- apache-airflow (PyPI): affected all versions; fixed in 2.11.1, 3.1.5rc1
- apache-airflow (PyPI): affected all versions; fixed in 2.11.1
- apache-airflow (PyPI): affected all versions; fixed in 2.11.1
- apache-airflow (PyPI): affected from 3.0.0b1; fixed in 3.1.5rc1
- apache-airflow (PyPI): affected from 3.0.0b1; fixed in 3.1.5rc1
- airflow (Bitnami): affected all versions; fixed in 2.11.1, 3.1.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-65995/ (Markdown: https://insights.sbomify.com/CVE-2025-65995/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-65995
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-65995
- OSV: https://osv.dev/vulnerability/CVE-2025-65995

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-65995/
Summaries are generated and may contain mistakes; the official description above is the record.