apache-airflow
Affected
- introduced
2.3.0, fixed2.6.1(ecosystem)
Fixed versions
2.6.1
Fix
- Fixed version
2.6.1pip install --upgrade apache-airflow==2.6.1
Advisory
Also known as: BIT-airflow-2023-51702, CVE-2023-51702, GHSA-mg2x-mggj-6955, PYSEC-2026-1144
Apache Airflow CNCF Kubernetes provider, Apache Airflow: Kubernetes configuration file saved without encryption in the Metadata and logged as plain text in the Triggerer service
Since version 5.2.0, when using deferrable mode with the path of a Kubernetes configuration file for authentication, the Airflow worker serializes this configuration file as a dictionary and sends it to the triggerer by storing it in metadata without any encryption. Additionally, if used with an Airflow version between 2.3.0 and 2.6.0, the configuration dictionary will be logged as plain text in the triggerer service without masking. This allows anyone with access to the metadata or triggerer log to obtain the configuration file and use it to access the Kubernetes cluster.
This behavior was changed in version 7.0.0, which stopped serializing the file contents and started providing the file path instead to read the contents into the trigger. Users are recommended to upgrade to version 7.0.0, which fixes this issue.
Medium Basis: CVSS v3 score 6.5, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
2.3.0, fixed 2.6.1 (ecosystem)2.6.1
2.6.1pip install --upgrade apache-airflow==2.6.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: PyPA Advisory Database · CC BY 4.0