Airflow is widely used; flaw enables code execution in Scheduler/API with access to DB creds and JWT secret—high-impact for many orgs.
CVE-2026-58076
Airflow deserialization bug allows arbitrary imports/exec in Scheduler/API leading to RCE and secret theft.
Is CVE-2026-58076 being exploited?
Not confirmed. CVE-2026-58076 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-58076?
CVE-2026-58076 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-58076?
Yes. A fix has been recorded for CVE-2026-58076. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-58076 affect?
CVE-2026-58076 affects Apache Airflow < 3.3.1, Airflow Scheduler, Airflow API server, Deployments using serialized DAGs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58076?
Upgrade to apache-airflow 3.3.1+, rotate DB/JWT secrets and review logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution in Scheduler/API via deserialized exception objects; attackers can run arbitrary callables and expose DB creds and JWT secret.
Immediate action required
- affected>= 3.0.0 and < 3.3.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.