Description
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.
Published: 2026-06-01
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in Apache Airflow’s connection retrieval API allows an authenticated user with Connection‑read permission to leak secrets that are stored in a connection’s extra JSON field. The bug bypasses the redaction allowlist, so credential fields such as those used by Slack providers are returned in plain text. This is an information‑exposure weakness (CWE‑200) that can reveal confidential service credentials and other sensitive data.

Affected Systems

Apache Airflow applications that use the default Connection‑read role and store credentials directly in the connection’s extra JSON blob are affected. The vulnerability is present in any version of Airflow prior to the fix that was shipped in release 3.2.2; users of these earlier versions should review their deployment for cut‑and‑paste credentials in connection blobs.

Risk and Exploitability

The attack requires an internal authenticated user who has been granted read access to the connection via the UI or API. Because the user must already have Connection‑read rights, the exploitation is restricted to roles that can query connection details. No exploitation probability score is available and the vulnerability is not listed in CISA’s KEV catalog, yet the exposure could have serious consequences if an attacker gains access to any user account with the necessary permission.

Generated by OpenCVE AI on June 1, 2026 at 08:51 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the Apache Airflow upgrade to version 3.2.2 or later, which removes the incomplete redaction flaw.
  • Configure deployments to store sensitive credential values in a secret‑backend instead of the Connection’s extra field, as recommended for defense‑in‑depth.
  • Restrict Connection‑read permissions to only those users or roles that truly need to view connection details, limiting the potential audience for exposed secrets.

Generated by OpenCVE AI on June 1, 2026 at 08:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 01 Jun 2026 09:30:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache airflow
Vendors & Products Apache
Apache airflow
References

Mon, 01 Jun 2026 07:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Apache Airflow: Incomplete Redaction of Sensitive Fields in Connection Extra API Response
Weaknesses CWE-200
References

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-06-01T07:44:01.595Z

Reserved: 2026-05-10T21:43:28.304Z

Link: CVE-2026-45192

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-06-01T08:16:20.567

Modified: 2026-06-01T09:16:19.390

Link: CVE-2026-45192

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-01T09:15:24Z

Weaknesses