Is CVE-2026-58076 exploited in the wild?

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

How severe is CVE-2026-58076?

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

Which products and versions are affected?

Apache Airflow prior to 3.3.1; 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-58076?

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-58076 attacked?

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

Am I affected by CVE-2026-58076?

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-58076: Apache Airflow unsafe exception deserialization remote code execution

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

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-58076 attacked?

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

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

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-58076 · Severity: high · CVSS 8.8 · Published 2026-08-12

Apache Airflow's Scheduler and API server deserialize exception data from serialized DAG definitions. A malicious DAG author can embed arbitrary Python code in the executor_config field that is executed when the Scheduler loads the DAG or when an authenticated user accesses the DAG via the API. The Scheduler and API server have full access to the metadata database and JWT signing credentials, making this a severe compromise vector that bypasses Airflow's security model.

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

Quick answers

Is CVE-2026-58076 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-58076 being exploited in the wild.
How severe is CVE-2026-58076?: High severity, with a CVSS score of 8.8, published 12 August 2026.
Which products and versions are affected?: Apache Airflow prior to 3.3.1; 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-58076?: 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-58076 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-58076?: 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"
```

Affected products

Apache Airflow prior to 3.3.1

Identifiers

CVE-2026-58076
BIT-AIRFLOW-2026-58076
GHSA-8prw-8m6x-8w6f
PYSEC-2026-3991

Timeline

2026-08-12: disclosed
2026-08-05: patched: PR #68511 merged to main

References

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