- Exploited
- No known exploitation
- Fix
- Fixed in 3.4.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.4.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache Airflow's bundled `example_dag_decorator` example Dag can be tricked into running shell commands on the worker through a crafted IPv6 zone identifier in an IP address fetched over HTTP. The bug only applies when example Dags are loaded (`load_examples` enabled), and an attacker would need to be able to trigger that Dag with a custom `url` parameter.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
The example_dag_decorator example Dag shipped with Apache Airflow validated an IP address fetched over HTTP with Python's ipaddress module and then placed it into a shell command. ipaddress accepts IPv6 zone identifiers containing arbitrary characters, so when example Dags are loaded (load_examples enabled), a user who can trigger that Dag with a custom url parameter could point it at a server whose response injects shell commands run on the worker. This is an incomplete fix for CVE-2025-54941; users who upgraded for CVE-2025-54941 should upgrade again. Users are advised to upgrade to apache-airflow 3.4.0 or later, or to disable example Dags (load_examples = False), which is recommended for production.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach12/20apache-airflow-core: 647K downloads a week
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
Impact
- Widely used
apache-airflow-core has 647k weekly downloads.Source: pypistats.org
473 packages depend on apache-airflow-core.Source: deps.dev
What to do
Upgrade to a fixed version: 3.4.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
From 3.0.5 · fixed in 3.4.0
Fixed in 3.4.0 (released Nov 6, 2026, 3 days before disclosure).
The latest release, 3.4.0, is not affected.
Evidence 3
- Advisory
- Patch
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-101031
Is CVE-2026-101031 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-101031?
apache-airflow-core (PyPI): from 3.0.5 before 3.4.0.Source: cve.now feed data
How do I fix CVE-2026-101031?
Upgrade to a fixed version: 3.4.0.Source: cve.now feed data