The vulnerability arises because JWT tokens for authenticating worker pods against the Execution API are passed as command-line arguments, making them visible in the pod spec. An attacker with read-only Kubernetes access to pods in the Airflow namespace can retrieve these tokens and impersonate running tasks to invoke state-changing API calls such as triggering DAG runs or modifying variables. This issue affects Apache Airflow deployments using the KubernetesExecutor. The fix requires upgrading Apache Airflow to version 3.2.2 or later, which complements the fix for CVE-2026-27173 in the related provider package.

An attacker with authenticated UI/API access and Kubernetes read-only permissions in the Airflow namespace can harvest JWT tokens from pod specifications and perform unauthorized state-mutating operations on the Execution API. This includes triggering DAG runs, clearing runs, and reading or writing sensitive configuration data such as Variables, Connections, and XComs. The vulnerability compromises confidentiality, integrity, and availability of the Airflow environment.

Users should upgrade Apache Airflow to version 3.2.2 or later to remediate this vulnerability. Deployments that have already upgraded apache-airflow-providers-cncf-kubernetes to 10.17.0 or later per CVE-2026-27173 must also upgrade apache-airflow to 3.2.2 or later to fully close the vulnerability. Patch status is not explicitly stated as 'official-fix' but the advisory strongly recommends upgrading to these versions. No alternative mitigations are provided.