Is CVE-2026-67587 exploited in the wild?

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

How severe is CVE-2026-67587?

High severity, with a CVSS score of 8.8, published 12 August 2026.

Which products and versions are affected?

Apache Airflow 3.0.0 through 3.3.0; apache-airflow (PyPI) >= 3.3.0, < 3.3.1, ECOSYSTEM:introduced=3.3.0,fixed=3.3.1.

Is there a fix for CVE-2026-67587?

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

How is CVE-2026-67587 attacked?

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

Am I affected by CVE-2026-67587?

Check whether you run Apache Airflow or apache-airflow (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-67587: Apache Airflow arbitrary module import via deserialized callback

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

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

Q: How is CVE-2026-67587 attacked?

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

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

Check whether you run Apache Airflow or apache-airflow (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-67587 · Severity: high · CVSS 8.8 · Published 2026-08-12

Apache Airflow is a workflow orchestration platform used to schedule and monitor data pipelines. A vulnerability in its Task SDK allows a DAG author to cause arbitrary Python modules to be imported within the scheduler process by crafting malicious serialized callback objects. An attacker exploiting this could execute arbitrary code on the scheduler, potentially compromising the entire orchestration infrastructure and any downstream systems it controls.

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

Quick answers

Is CVE-2026-67587 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67587 being exploited in the wild.
How severe is CVE-2026-67587?: High severity, with a CVSS score of 8.8, published 12 August 2026.
Which products and versions are affected?: Apache Airflow 3.0.0 through 3.3.0; apache-airflow (PyPI) >= 3.3.0, < 3.3.1, ECOSYSTEM:introduced=3.3.0,fixed=3.3.1.
Is there a fix for CVE-2026-67587?: Yes. apache-airflow (PyPI): upgrade to 3.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67587 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-67587?: Check whether you run Apache Airflow or apache-airflow (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 (PyPI): upgrade to 3.3.1 or later
```
pip install "apache-airflow>=3.3.1"
```

Technical details

The vulnerability is a deserialization attack in Apache Airflow's Task SDK. When deserializing a `Callback` object from stored `next_kwargs`, the SDK reconstructs the callback by re-running its constructor, which imports the module specified in the stored callback path. The `SyncCallback` class passes the default `allowed_deserialization_classes` allow-list, so standard mitigation measures do not prevent this attack. A DAG author (who controls a task instance's `next_kwargs` through the task execution API) can inject a malicious callback path that triggers arbitrary module imports during the scheduler's `awaiting_input` timeout sweep. The sweep runs unconditionally and requires no non-default configuration. This is a distinct gadget from CVE-2026-58076 and CVE-2026-67260, affecting only Airflow 3.0.0 through 3.3.0.

Affected products

Apache Airflow 3.0.0 through 3.3.0

Identifiers

CVE-2026-67587
BIT-AIRFLOW-2026-67587
GHSA-2qjv-p2gc-mjg2
PYSEC-2026-3708

Timeline

2026-08-12: disclosed
2026-08-04: patched: Fix merged in PR #70704; upgrade to 3.3.1 or later

References

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