Skip to content

Patch apache-airflow security advisories (bump to 2.11.1) - #6

Open
Mrassimo wants to merge 3 commits into
mainfrom
fix/airflow-security-cve
Open

Patch apache-airflow security advisories (bump to 2.11.1)#6
Mrassimo wants to merge 3 commits into
mainfrom
fix/airflow-security-cve

Conversation

@Mrassimo

@Mrassimo Mrassimo commented Jul 11, 2026

Copy link
Copy Markdown
Owner

Addresses the Dependabot apache-airflow advisories. Bumps to the latest 2.x release, 2.11.1, in both requirements-dev.txt and pyproject.toml.

What this fixes

CVE Issue Affects 2.x? Patched
CVE-2024-56373 LogTemplate code injection (web-server) ✅ yes 2.11.1
CVE-2025-68675 Proxy credentials leak in task logs ✅ yes 2.11.1

Why not upgrade to 3.x

The other two alerts are only "patched" in the 3.x line, but neither actually affects a 2.x deployment:

  • CVE-2025-54550 (example_xcom RCE) — per the advisory, "does not affect Airflow release; example_dags are not supposed to be enabled in production." It's an unsafe example/doc pattern, and this project runs with AIRFLOW__CORE__LOAD_EXAMPLES=False.
  • CVE-2026-45360 (deserialization via DeadlineReference) — the vulnerable Deadline feature is Airflow 3.x-only; the code path does not exist in 2.x.

Going to 3.x would be a major migration (Dockerfile base image → Python ≥3.10, webserverapi-server, db initdb migrate, DAG import paths, schedule_interval/provide_context removals) that couldn't be validated here — and would introduce the feature the deserialization CVE lives in. Staying on the patched 2.x line is the lower-risk fix.

Changes

  • apache-airflow: >=2.7.0,<2.10.0>=2.11.1,<3.0.0
  • apache-airflow-providers-docker: >=3.5.0,<3.14.0>=3.9.0,<4.0.0 (2.x-compatible)
  • Same floors applied in pyproject.toml

No DAG, Dockerfile, or compose changes required. dags/ahgd_pipeline.py remains 2.x-compatible.

🤖 Generated with Claude Code

@Mrassimo Mrassimo changed the title Fix apache-airflow security advisories (4 CVEs) Patch apache-airflow security advisories (bump to 2.11.1) Jul 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant