When a DAG failed during parsing, Airflow’s error-reporting in the UI could include the full kwargs passed to the operators. If those kwargs contained sensitive values (such as secrets), they might be exposed in the UI tracebacks to authenticated users who had permission to view that DAG.
The issue has been fixed in Airflow 3.1.5rc1 and 2.11.1, and users are strongly advised to upgrade to prevent potential disclosure of sensitive information.
{
"github_reviewed": true,
"github_reviewed_at": "2026-02-25T15:42:56Z",
"severity": "MODERATE",
"nvd_published_at": "2026-02-21T03:15:57Z",
"cwe_ids": [
"CWE-209"
]
}