CVE-2026-58076: Apache Airflow Arbitrary Code Execution via Serialization Layer
Summary
CVE-2026-58076: 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... Affects apache-airflow versions >= 3.3.0, < 3.3.1. Fixed in 3.3.1. How to fix ↓
Also tracked for
- airflow · Bitnami
The same CVE-2026-58076 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache Airflow is an open-source platform designed to programmatically author, schedule, and monitor workflows. It allows users to define complex workflows as Directed Acyclic Graphs (DAGs) and provides a rich user interface to manage these workflows. However, due to its flexible serialization layer, it is vulnerable to arbitrary code execution, which can pose significant security risks if exploited.
Vulnerability Detail
The vulnerability arises from Apache Airflow's serialization layer, which reconstructs exception nodes by calling import_string() on class names extracted from serialized data. This process lacks restrictions on what can be imported, enabling a malicious actor to manipulate the executor_config of an operator. By doing so, they can trigger the import and execution of arbitrary callables, such as subprocess.check_output or builtins.eval. This vulnerability affects both the Scheduler and the API server, which are critical components that should not execute user-defined code. The potential ramifications include unauthorized access to sensitive metadata database credentials and JWT signing secrets, making this a severe security issue with a CVSS score of 8.8.
How To Fix
Latest published version: 3.3.2 as of 22 Oct 2026
pip install --upgrade "apache-airflow==3.3.2"Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
3.3.1
This is the first release that contains the fix.
pip install --upgrade "apache-airflow==3.3.1"Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
Currently, there are no specific workarounds mentioned to mitigate this vulnerability without upgrading the package. The best course of action is to apply the patch by upgrading to the latest version.
Conclusion
The CVE-2026-58076 vulnerability in Apache Airflow poses a significant risk due to its potential for arbitrary code execution. Users are strongly advised to upgrade to version 3.3.1 or later to mitigate this risk. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for apache-airflow →
FAQ
CVE-2026-58076 is a vulnerability in Apache Airflow that allows for arbitrary code execution through its serialization layer.
An attacker can manipulate the executor_config in a DAG to import and execute arbitrary code, potentially leading to unauthorized access to sensitive information.
Versions of Apache Airflow prior to 3.3.1 are affected by this vulnerability.
While there are no specific workarounds, it is crucial to prioritize upgrading to the patched version to ensure security.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
References
Related vulnerabilities
Recent vulnerabilities recorded for apache-airflow.
