Homepage

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

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.39% (31st 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-20416199
  • published4 Oct 2026
  • disclosed12 Aug 2026
Report a new vulnerability Found a mistake?

Introduced: 12 Aug 2026

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

How to fix?

Upgrade Minimos:latest airflow-3 to version 3.3.1-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.

Apache Airflow's Config API did not mask team-scoped sensitive configuration values in multi-team deployments. When an administrator has enabled multi-team mode and exposed the Config API, an authenticated Viewer holding only configuration-read access — with no prior access to the secret — could read a team-scoped Celery broker URL, including its embedded credentials, in cleartext, while the equivalent global option was correctly masked. The secrets masker matched only base section and option names and did not normalize team-prefixed sections before the sensitivity check (CWE-200). This is a distinct masker bypass from CVE-2026-48828 and CVE-2026-48892: deployments that upgraded to apache-airflow 3.3.0 to address those issues remain affected by this team-scoped variant. Users are advised to upgrade to apache-airflow 3.3.1 or later, which normalizes team-scoped sections before masking.