CVE-2026-25219 Affecting airflow-2-advanced-compat package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (6th 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-AIRFLOW2ADVANCEDCOMPAT-16300391
  • published27 Apr 2026
  • disclosed15 Apr 2026

Introduced: 15 Apr 2026

NewCVE-2026-25219  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest airflow-2-advanced-compat.

NVD Description

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

The access_key and connection_string connection properties were not marked as sensitive names in secrets masker. This means that user with read permission could see the values in Connection UI, as well as when Connection was accidentaly logged to logs, those values could be seen in the logs. Azure Service Bus used those properties to store sensitive values. Possibly other providers could be also affected if they used the same fields to store sensitive data.

If you used Azure Service Bus connection with those values set or if you have other connections with those values storing sensitve values, you should upgrade Airflow to 3.1.8