Is CVE-2026-49298 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-49298 being exploited in the wild.

How severe is CVE-2026-49298?

High severity, with a CVSS score of 8.8, published 1 June 2026.

Which products and versions are affected?

Apache Airflow < 3.2.2; apache-airflow-core (PyPI) < 3.2.2, ECOSYSTEM:introduced=0,fixed=3.2.2.

Is there a fix for CVE-2026-49298?

Yes. apache-airflow-core (PyPI): upgrade to 3.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-49298 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-49298?

Check whether you run Apache Airflow or apache-airflow-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49298: Apache Airflow information disclosure in KubernetesExecutor pod spec

Q: Which products and versions are affected?

Apache Airflow < 3.2.2; apache-airflow-core (PyPI) < 3.2.2, ECOSYSTEM:introduced=0,fixed=3.2.2.

Q: Is there a fix for CVE-2026-49298?

Yes. apache-airflow-core (PyPI): upgrade to 3.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-49298 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-49298?

Check whether you run Apache Airflow or apache-airflow-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49298 · Severity: high · CVSS 8.8 · Published 2026-06-01

A security flaw in Apache Airflow's KubernetesExecutor causes sensitive authentication tokens (JWTs) to be exposed in plain text within Kubernetes pod configurations. An attacker with basic read-only access to the Kubernetes cluster could steal these tokens to impersonate a running task. This would allow them to unauthorizedly trigger or clear workflows, and read or modify sensitive business data such as Variables, Connections, and XComs.

Technologies: Apache Airflow, apache-airflow-core (PyPI). Vendors: Apache, PyPI.

Quick answers

Is CVE-2026-49298 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-49298 being exploited in the wild.
How severe is CVE-2026-49298?: High severity, with a CVSS score of 8.8, published 1 June 2026.
Which products and versions are affected?: Apache Airflow < 3.2.2; apache-airflow-core (PyPI) < 3.2.2, ECOSYSTEM:introduced=0,fixed=3.2.2.
Is there a fix for CVE-2026-49298?: Yes. apache-airflow-core (PyPI): upgrade to 3.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49298 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-49298?: Check whether you run Apache Airflow or apache-airflow-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

apache-airflow-core (PyPI): upgrade to 3.2.2 or later
```
pip install "apache-airflow-core>=3.2.2"
```

Technical details

A vulnerability in Apache Airflow's KubernetesExecutor (CWE-538) causes JWT tokens used for Execution API authentication to be passed as command-line arguments to worker containers. These arguments are visible in the Kubernetes pod specification, making them accessible to any user with 'pods/get' permissions in the Airflow namespace. An attacker can harvest these tokens to call state-mutating Execution API endpoints, enabling them to trigger DAG runs, clear runs, or manipulate Variables, Connections, and XComs. This issue is the core-side component of a coordinated fix (alongside CVE-2026-27173). Users should upgrade to apache-airflow 3.2.2 or later.

Affected products

Apache Airflow < 3.2.2

Identifiers

CVE-2026-49298
GHSA-5j6p-jrrm-6x94
PYSEC-2026-2358

Timeline

2026-06-01: disclosed
2026-06-01: advisory
2026-06-01: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.