Quick answers
- Is CVE-2026-101031 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101031 being exploited in the wild.
- How severe is CVE-2026-101031?
- 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-101031?
- Yes: fixed in Apache Airflow 3.4.0. Until then: Disable example Dags by setting load_examples = False in the Airflow configuration, which is recommended for production deployments. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-101031 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-101031?
- 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
Disable example Dags by setting load_examples = False in the Airflow configuration, which is recommended for production deployments.
Technical details
The example_dag_decorator validates an IP address fetched over HTTP using Python's ipaddress module and then inserts it into a shell command. The ipaddress module accepts IPv6 zone identifiers with arbitrary characters, allowing shell metacharacters to bypass validation. An attacker who can trigger the Dag with a custom url parameter can point it to a malicious server whose HTTP response contains shell commands that execute on the worker. This is an incomplete fix for CVE-2025-54941.
Affected products
- Apache Airflow before 3.4.0
Timeline
- 2026-11-09: disclosed