An authorization bypass vulnerability exists in the Ansible Automation Platform (AAP) gateway API that permits an authenticated administrator to create new service keys for the Controller service cluster outside the installer-provisioned path. These administrator-issued keys are cryptographically indistinguishable from legitimate keys and can be used to forge service-authentication tokens impersonating the Controller service. When combined with the gateway's OIDC workload-identity endpoint (enabled via FEATURE_OIDC_WORKLOAD_IDENTITY_ENABLED), attackers can coerce the gateway to sign Workload Identity Tokens (WITs) for arbitrary Controller workloads. Downstream resource servers trusting the gateway OIDC key, such as HashiCorp Vault, will accept these forged WITs and disclose AAP credentials bound to those workloads, thereby breaching the attacker's authorization boundary. The vulnerability leads to read-only disclosure of credentials used by AAP to automate managed infrastructure. Service keys created by administrators persist across upgrades, so auditing and revocation of non-installer-provisioned keys is critical. Disabling the workload-identity endpoint and rotating downstream credentials are recommended mitigations.

The vulnerability allows an attacker with administrator privileges to bypass authorization controls and forge authentication tokens that impersonate the Controller service. This leads to unauthorized disclosure of AAP credentials from downstream resource servers such as HashiCorp Vault. The exposed credentials may include sensitive automation keys like cloud IAM keys, SSH private keys, or service-account credentials. The impact scope is changed because it extends beyond the gateway to trusted downstream services. The real-world business impact depends on the deployment and the nature of the credentials exposed. The vulnerability does not affect integrity or availability but results in high confidentiality impact.

Red Hat advises auditing and revoking any Controller service keys not provisioned by the installer, especially for environments upgraded from AAP 2.5 or 2.6. If the workload-identity integration is not required, set FEATURE_OIDC_WORKLOAD_IDENTITY_ENABLED=false to disable the workload-identity endpoint. Additionally, rotate any downstream credentials (e.g., in HashiCorp Vault) that could have been accessed via forged workload identity tokens. These steps are the primary mitigations and should be prioritized. No official patch or fix version is explicitly stated in the advisory; check the vendor advisory for updates.