The vulnerability in Apache Airflow's environment-variable secrets backend arises from improper authorization checks when resolving team-scoped Connections or Variables. The guard designed to restrict access to the correct team scope only operates when no team scope is supplied and fails to match team names containing underscores, which are valid. Consequently, the lookup falls back to an unconditional global read of environment variables, allowing an authenticated user in multi-team mode to access another team's Connection credentials via the POST /api/v2/connections/test endpoint. This endpoint uses the credentials for authentication outward rather than returning them. Exploitation requires multi-team mode enabled, test_connection set to Enabled (not the default), team-scoped secrets provisioned as environment variables, and knowledge of the encoded identifier. Redirecting the test to an attacker-controlled host is blocked separately. The issue is addressed in Apache Airflow version 3.3.1 and later.

An authenticated user in one team can bypass authorization controls to access and use another team's Connection credentials in multi-team mode. This could lead to unauthorized outbound authentication using another team's credentials, potentially compromising confidentiality and integrity of team-specific resources. The vulnerability requires specific configuration and knowledge, limiting its exposure to certain deployments.

Users should upgrade to Apache Airflow version 3.3.1 or later, where this issue is fixed. Until then, ensure that multi-team mode is disabled or that test_connection remains set to Disabled (the default). Additionally, avoid provisioning team-scoped secrets as environment variables in the API-server process if possible. Patch status is not explicitly confirmed in the advisory, but the vendor advises upgrading to 3.3.1 or later for remediation.