Skip to content
VulniPulse
High8.8Apache Software Foundation

CVE-2026-58076: Apache Airflow: Unguarded import_string of airflow_exc_ser / base_exc_ser exception nodes in BaseSerialization.deserialize enables DAG-author RCE on Scheduler / API Server

This Apache advisory covers CVE-2026-58076 in Apache Airflow.

Open the Apache advisory

Key facts

Vendor rating
High, CVSS 8.8
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H · base score 8.8, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: high.
Weakness
  • CWE-502: Deserialization of Untrusted Data
EPSS
0.48% chance of exploitation in the next 30 days (42nd percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
Apache Airflow 3.0.0 before 3.3.1
Fixed in
3.3.1
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationAirflow

Description

Apache Airflow's serialization layer reconstructed exception nodes by calling `import_string()` on a class name taken from the serialized blob and instantiating it with arguments from the same blob, with no restriction on what could be imported.

An operator's `executor_config` reaches that branch, so a Dag author could place a value there that causes an arbitrary callable to be imported and invoked -- for example `subprocess.check_output`, or `builtins.eval` on the `builtins`-prefixed variant.

The code runs in the **Scheduler**, which reconstructs serialized Dags in its normal loop with no request involved, and in the **API server**, on any authenticated read of the Dag such as `GET /api/v2/dags/{dag_id}/details`.

Both are components the Airflow security model states must never execute Dag-author code, and both hold the metadata database credentials and the JWT signing secret. No non-default configuration is required.

This is a **different sink from CVE-2026-33264**, which covered only the trigger branch of the same deserializer: deployments that upgraded in response to that advisory are still affected through the exception branch and must upgrade again.

Users are advised to upgrade to apache-airflow 3.3.1 or later, which restricts the imported class to a subclass of `BaseException`.

Text from the source record.

Affected versions
  • Apache Airflow 3.0.0 before 3.3.1

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-58076

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • This is a **different sink from CVE-2026-33264**, which covered only the trigger branch of the same deserializer: deployments that upgraded in response to that advisory are still affected through the exception branch and must upgrade again.
  • Users are advised to upgrade to apache-airflow 3.3.1 or later, which restricts the imported class to a subclass of `BaseException`.

Support dates for the fixed release lines

All end-of-life dates for Apache Airflow

Apache Software Foundation advisories, August 2026All Apache Software Foundation advisories

Get an email when Apache Airflow publishes the next one.

See Apache Airflow's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache Airflow