CyberRota Analysis
AI-GeneratedApache Airflow versions 1.15.0 to 2.0.0 are vulnerable due to the ability of users with connection-editing privileges to execute arbitrary code in the control plane by manipulating the `extra` field of Kafka connections. This flaw primarily affects deployments with the Kafka event producer enabled, potentially allowing unauthorized access to the scheduler process. Organizations using Apache Airflow with Kafka integrations, particularly those not utilizing Google Managed Kafka, should prioritize upgrading to version 2.0.0 or later to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Apache Airflow Apache Kafka provider versions 1.15.0 before 2.0.0 resolve dotted-path strings found in a Kafka connection's `extra` field into Python callables via `import_string`, with no allowlist, and hand them to the confluent-kafka client which invokes them. Deployments that have enabled the Kafka event producer — `dag_run_events_enabled` or `task_instance_events_enabled`, both disabled by default — build that client inside the scheduler process, so a user whose only privilege is editing Airflow connections gains arbitrary code execution in the control plane; the Airflow security model limits connection-configuration users to code execution on workers, not the scheduler. Deployments using Google Managed Kafka are not affected, because that code path overwrites any user-supplied `oauth_cb`; plain brokers and Amazon MSK are exposed. Users are recommended to upgrade to apache-airflow-providers-apache-kafka 2.0.0 or later, which adds an allowlist configuration option for connection-string callbacks.
Related CVEs
Other vulnerabilities affecting the same vendor(s)