See bug report https://issues.redhat.com/browse/AAP-59025 Create a Personal Access Token (PAT) on Gateway, the user account in this was an admin account. Configure the token's scope to be read-only. Use the token to attempt a write operation on the Controller component. The write operation proceeds despite the token being read-only. Attempt to create a new team on Gateway and the operation correctly fails as Gateway uses the read-only scope. While the user account was an admin account, the token's read-only scope should have been acknowledged. This does not feel like a true escalation of privileges vulnerability since the user account was an admin.
This issue has been addressed in the following products: Red Hat Ansible Automation Platform 2.6 for RHEL 9 Via RHSA-2026:0360 https://access.redhat.com/errata/RHSA-2026:0360
This issue has been addressed in the following products: Red Hat Ansible Automation Platform 2.5 for RHEL 8 Red Hat Ansible Automation Platform 2.5 for RHEL 9 Via RHSA-2026:0361 https://access.redhat.com/errata/RHSA-2026:0361