Quick answers
- Is CVE-2026-82337 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82337 being exploited in the wild.
- How severe is CVE-2026-82337?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Apache Airflow before 3.4.0.
- Is there a fix for CVE-2026-82337?
- Yes: fixed in Apache Airflow 3.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82337 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82337?
- Check whether you run Apache Airflow 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
- Fixed in: Apache Airflow 3.4.0
Technical details
Generic deserialization in the decode_deadline_alert function passes DAG-author-controlled `callback` and `interval` fields to airflow.sdk.serde.deserialize, which imports and instantiates classes by name from a security allowlist. The vulnerability occurs in the scheduler and API server when loading serialized DAGs. This is a partial regression from CVE-2026-45360, which hardened only the `reference` field; the `callback` and `interval` fields remain vulnerable to the same attack.
Affected products
- Apache Airflow before 3.4.0
Timeline
- 2026-11-09: disclosed
- 2026-09-18: patched: Fix merged in PR #72651