# CVE-2025-66388: Apache Airflow: Secrets in rendered templates not redacted properly and exposed in the UI

> Authenticated users can view unredacted secrets in rendered templates, exposing sensitive data to unauthorized personnel.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 15 Dec 2025
- **Updated:** 16 Dec 2025
- **Also known as:** BIT-airflow-2025-66388, GHSA-fv47-pqh6-wxgq, MINI-vxhx-rmxh-q79x, PYSEC-2025-86

## What is CVE-2025-66388?

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

### Official description

A vulnerability in Apache Airflow allowed authenticated UI users to view secret values in rendered templates due to secrets not being properly redacted, potentially exposing secrets to users without the appropriate authorization.

Users are recommended to upgrade to version 3.1.4, which fixes this issue.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apache-airflow` | PyPI | From 3.1.0 | 3.1.4 |
| `apache-airflow` | PyPI | From 3.1.0 | 3.1.5 |
| `apache-airflow` | PyPI | From 3.1.0 | 3.1.5 |
| `airflow` | Bitnami | From 3.1.0 | 3.1.4 |

Products: Apache Airflow.

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

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

## Is CVE-2025-66388 being exploited?

There is no known exploitation of CVE-2025-66388 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-66388 and fix it if it is affected.

What it is: CVE-2025-66388 is a medium-severity vulnerability in Apache Airflow, published on 15 Dec 2025. 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-66388 in the wild and no public exploit code.

Affected packages and fixed versions:
- apache-airflow (PyPI): affected from 3.1.0; fixed in 3.1.4
- apache-airflow (PyPI): affected from 3.1.0; fixed in 3.1.5
- apache-airflow (PyPI): affected from 3.1.0; fixed in 3.1.5
- airflow (Bitnami): affected from 3.1.0; fixed in 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-66388/ (Markdown: https://insights.sbomify.com/CVE-2025-66388/index.md)
```

## Sources

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

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