Deployments using plain Kafka brokers or Amazon MSK are exposed when the Kafka event producer is enabled through either dag_run_events_enabled or task_instance_events_enabled. Both settings are disabled by default, so deployments that have not enabled either event type do not build the affected client in the scheduler process.
An attacker needs permission to edit Airflow connections and must be able to place a dotted Python path in the Kafka connection extra configuration. The vulnerable provider resolves that path and supplies the resulting callable to the Kafka client.
No. The Google Managed Kafka code path replaces any user-supplied oauth_cb value, preventing the affected callback configuration from being used.
Upgrade apache-airflow-providers-apache-kafka to version 2.0.0 or later. This release adds an allowlist configuration option for connection-string callbacks.