apache-airflow
Affected
- introduced
0, fixed3.3.1(ecosystem)
Fixed versions
3.3.1
Fix
- Fixed version
3.3.1pip install --upgrade apache-airflow==3.3.1
Advisory
Also known as: BIT-airflow-2026-68969, CVE-2026-68969, PYSEC-2026-3711
Apache Airflow bulk endpoints log Variable and Connection secrets in cleartext
Apache Airflow wrote Variable values and Connection extra contents to the audit log in cleartext when they were submitted through the bulk endpoints (PATCH /api/v2/variables and PATCH /api/v2/connections). The audit-log masking recognised only top-level request fields, and a bulk request nests its entities two levels below, so no masking was applied to them. Any authenticated user with audit-log read access -- who need not hold Variables or Connections read at all -- could recover those secrets verbatim, and the Connection extra copy is stored unencrypted in the log while the connection table encrypts it. The Airflow UI's *Import Variables* action posts to this endpoint, so an ordinary operator import wrote every secret in the file to the log. This is a different code path from CVE-2026-50204: that fix shipped in 3.3.0 and covers the single-entity endpoints only, so deployments that upgraded in response to that advisory remain affected and must upgrade again. Users are advised to upgrade to apache-airflow 3.3.1 or later.
Medium Basis: The source's own band: MODERATE
0, fixed 3.3.1 (ecosystem)3.3.1
3.3.1pip install --upgrade apache-airflow==3.3.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0