Homepage

Information Exposure Affecting airflow-3 package, versions <3.2.2-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.43% (35th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-AIRFLOW3-17898079
  • published9 Jul 2026
  • disclosed1 Jun 2026
Report a new vulnerability Found a mistake?

Introduced: 1 Jun 2026

CVE-2026-45192  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade Minimos:latest airflow-3 to version 3.2.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream airflow-3 package and not the airflow-3 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.