A bug in the GET `/api/v2/connections/{connection_id}` REST API endpoint in Apache Airflow allowed an authenticated UI/API user with Connection-read permission to retrieve secrets stored in a Connection's `extra` JSON blob under field names not present in the redaction allowlist (`DEFAULT_SENSITIVE_FIELDS`) — for example, official Slack-provider credential field names were returned in plaintext. Affects deployments that store credentials in Connection `extra` blobs and grant Connection-read access to multiple users. Users are advised to upgrade to `apache-airflow` 3.2.2 or later. As a defense-in-depth mitigation, deployment operators can store sensitive credential values in a secret-backend rather than inlined into the Connection's `extra` field.
References
| Link | Resource |
|---|---|
| https://github.com/apache/airflow/pull/66673 | Issue Tracking Patch |
| https://lists.apache.org/thread/r2q93dg2wp5h9sd9vh6y4y5ljqd9crdd | Mailing List Vendor Advisory |
| http://www.openwall.com/lists/oss-security/2026/06/01/3 | Mailing List Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-06-01 08:16
Updated : 2026-07-21 18:10
NVD link : CVE-2026-45192
Mitre link : CVE-2026-45192
CVE.ORG link : CVE-2026-45192
JSON object : View
Products Affected
apache
- airflow
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor
