Skip to content
fr Sign in
Not rated

CVE-2026-49298 A bug in Apache Airflow's KubernetesExecutor caused JWT tokens used by worker pods to authenticate against the Execution…

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.

Affected products and versions

Product Affected versions Fixed in
Apache Airflow 3.0 3.0.0 → < 3.2.2 3.2.2

References

Timeline

  1. Published
  2. Last modified

Other CVEs of Apache Airflow

The 153 CVEs of Apache Airflow →
CVE-2026-86473 Apache Airflow: the Core API logout endpoint revokes only a session token presented as the _token cookie Not rated CVE-2026-75158 Apache Airflow's `/assets/events` API returned asset events for every Dag in the deployment, with no filter… Not rated CVE-2026-82355 When a request to the Airflow core API carries both a session cookie and an explicit `Authorization: Bearer` token,… Not rated CVE-2026-75157 Apache Airflow's asset queued-events DELETE endpoints checked the caller's Dag-axis permission with `READ` instead of… Not rated
Track this CVE