Apache Airflow's Task SDK rebuilt a `Callback` object from serialized data by re-running its constructor, which imports
Apache Airflow's Task SDK rebuilt a `Callback` object from serialized data by re-running its constructor, which imports the module named by the stored callback path. Because `SyncCallback` is itself an Airflow class it passes the default `allowed_deserialization_classes` allow-list, so tightening that setting does not help. A Dag author — who controls a task instance's `next_kwargs` through the task execution API — can therefore cause an arbitrary module to be imported inside the scheduler proce
Affected packages
- apache-airflow— 3.3.0 → 3.3.1
Exploit signal
- Known exploited (CISA KEV)
- No
- EPSS score
- —
- EPSS percentile
- —
EPSS is the probability a CVE is exploited in the wild; percentile is its rank among all CVEs.
Sources
- https://www.cve.org/CVERecord?id=CVE-2026-58076
- https://www.cve.org/CVERecord?id=CVE-2026-67260
- https://lists.apache.org/thread/o00ww4n69qojvsckb464dtwd2nhzy6t0
- https://github.com/apache/airflow/pull/70704
Structured record: https://osv.dev/vulnerability/PYSEC-2026-3708
Recommended response stack
Some links are affiliate links — HackTribune may earn a commission at no extra cost to you.
Get incidents like this as alerts for your stack.
Join the beta