GPU VulnDB

Database/Control plane, storage & DevOps

Apache Airflow: incomplete CVE-2026-67260 fix still lets next_kwargs run constructors in the scheduler

UnscoredCVE-2026-96285Control plane, storage & DevOpscurated

Impact

The 3.3.1 fix for CVE-2026-67260 checks that the decoded next_kwargs is a dictionary, but only after deserializing the whole stored payload. Deserialization rebuilds nested objects of allow-listed classes, which include Airflow's own classes by default, and runs their constructors before the check can reject the value. A Dag author controls next_kwargs through the task execution API, so they can still trigger constructor execution in the scheduler (during the awaiting_input timeout sweep) and in the API server (when the task instance is served to a worker on an older Execution API version). No non-default configuration is required.

Who can reach it

A Dag author who can run tasks, acting through the task execution API. Authentication (Dag deployment rights) is required. Only versions 3.3.0 and later are affected.

What to do

Upgrade to apache-airflow 3.4.0 or later and restart the scheduler and API server. Deployments that moved to 3.3.1 for CVE-2026-67260 are still affected and must upgrade again. Versions before 3.3.0 are not affected.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.