# CVE-2026-82337: Apache Airflow unsafe deserialization in deadline alert fields

Source: https://junglewise.ai/threats/cve-2026-82337-apache-airflow-rebuilt-deadline-alert-fields-through-generic  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-09. Updated: 2026-11-09  
License: CC BY 4.0 with a link back

CVE-2026-82337 · Severity: info · Published 2026-11-09

Apache Airflow is a workflow orchestration platform used to manage data pipelines. A flaw in how the system deserializes deadline alert configuration allows a person writing a workflow (DAG author) to instantiate arbitrary classes within Airflow's allowlist in the scheduler and API server processes, potentially leading to code execution. This is an incomplete fix of a prior vulnerability that only patched one of three vulnerable fields.

Technologies: [Apache Airflow](https://junglewise.ai/threats/technologies/airflow). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## 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

## References

- [https://pypi.python.org/](https://pypi.python.org/)
- [https://github.com/apache/airflow/pull/72651](https://github.com/apache/airflow/pull/72651)

## Related threats

- [Apache Airflow incomplete deserialization check bypass in scheduler](https://junglewise.ai/threats/cve-2026-96285-apache-airflow-3-3-1-shipped-a-fix-for-that-checks-the-scheduler)
- [Apache Airflow scheduler XCom deserialization privilege escalation](https://junglewise.ai/threats/cve-2026-86829-apache-airflow-s-scheduler-fully-deserializes-xcom-values-written)
- [Apache Airflow CLI audit log secrets exposure](https://junglewise.ai/threats/cve-2026-86468-apache-airflow-s-cli-records-its-arguments-in-the-audit-log-but)
- [Apache Airflow Task SDK secret cache key collision in multi-team deployments](https://junglewise.ai/threats/cve-2026-76185-apache-airflow-s-task-sdk-secret-cache-built-its-keys-from-the)
- [Apache Airflow CeleryExecutor callback code execution](https://junglewise.ai/threats/cve-2026-68982-apache-airflow-s-celeryexecutor-ran-callback-workloads)