Advisory record · GHSA-q4c3-7575-55j2

Apache Airflow 3.3.0 moved human-in-the-loop tasks from the triggerer to a new `awaiting_input` task state swept by the scheduler. That sweep deserializes the task instance's `next_kwargs` without ...

CVSS 7.3 HighEPSS 0.0078 · 56th percentile

Published by the GitHub Advisory Database at 12 Aug 2026, 16:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
apache-airflowPyPI>=3.3.0, <3.3.13.3.1
Identifiers
GHSA-q4c3-7575-55j2 · BIT-airflow-2026-67260 · CVE-2026-67260 · PYSEC-2026-3707
Weakness (CWE)
CWE-502
Published
12 Aug 2026
Updated
15 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Airflow versions 3.3.0 up to but not including 3.3.1 are vulnerable. A Dag author, who can control a task instance's stored keyword arguments through the task execution API, can trigger arbitrary module import and object instantiation inside the scheduler process or stop the scheduler job; no non-default configuration is needed. Upgrade to apache-airflow 3.3.1 or later. Deployments that applied the fix for CVE-2026-58076 must also upgrade.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.3 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L OSV
  • CISA KEV Not listed.
  • EPSS 0.0078, the 56th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 12 Aug 2026, 15:33 UTC Confirmed by the CVE List
  2. 12 Aug 2026, 16:17 UTC Confirmed by NVD
  3. 31 Oct 2026, 14:08 UTC First seen by agentprime
  4. 31 Oct 2026, 14:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.