CVE 8.8 HIGH

Apache Airflow: JWT Token Exposure in KubernetesExecutor Command-Line Arguments_CVE-2026-49298

8.8 / 10
HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Description

A bug in Apache Airflow's KubernetesExecutor caused JWT tokens used by worker pods to authenticate against the Execution API to be passed to the worker container as command-line arguments visible in the pod spec. An authenticated UI/API user with Kubernetes read-only access to the cluster (e.g. `pods/get` in the Airflow namespace) could harvest the JWT from `kubectl describe pod` output and then call state-mutating Execution API endpoints — triggering Dag runs, clearing runs, reading or writing Variables / Connections / XComs — as if they were a running task. Affects deployments using the `KubernetesExecutor`. Users are advised to upgrade to `apache-airflow` 3.2.2 or later. This is the airflow-core half of the same vulnerability addressed by [CVE-2026-27173](https://www.cve.org/CVERecord?id=CVE-2026-27173), which shipped the apache-airflow-providers-cncf-kubernetes side of the fix. Deployments that already upgraded `apache-airflow-providers-cncf-kubernetes` to 10.17.0 or later per the CVE-2026-27173 advisory should additionally upgrade `apache-airflow` to 3.2.2 or later to close the core-side surface — the two fixes are complementary, not duplicates.

AI Analysis

JWT token exposure in KubernetesExecutor command-line arguments, allowing authenticated users to harvest and misuse tokens for state-mutating Execution API calls

Basic Information

ID CVE-2026-49298
Source apache
Published Jun 1, 2026 at 07:34
Modified Jun 2, 2026 at 16:43

Affected Product

Vendor Apache Software Foundation
Product Apache Airflow
Affected Versions Apache Software Foundation Apache Airflow 0

CWE Classification

AI Assessment

AI Score 8.8 / 10
AI Severity High
Vendor Apache Software Foundation
Product Apache Airflow
Version < 3.2.2

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.