The Auth.GetUserPrivateKey API performs a symbolic link resolution before accessing the specified SSH private key file. An attacker who is already authenticated can replace their own ~/.ssh/id_rsa with a symbolic link that points to any file on the host shared with the cluster‑manager EC2 instance. Because the cluster‑manager runs as root, the API then reads the target file and returns its contents, enabling confidential data disclosure such as other users’ SSH keys and application secrets. The vulnerability is a classic path traversal/indirect file read flaw (CWE‑59).

All versions of the AWS RES platform that are running on AWS infrastructure before the 2026.06 release are affected. The solution recommends upgrading to RES version 2026.06 or later. The vulnerability exists in the cluster‑manager component that handles user credential requests.

The CVSS score of 7.1 indicates a high severity, while the EPSS score is <1%, suggesting no known widespread exploitation yet. The vulnerability requires a valid authenticated session and the ability to send requests to Auth.GetUserPrivateKey. Because the cluster‑manager runs as root, any file readable by root becomes potentially accessible, raising significant confidentiality risks. The vulnerability is not listed in the CISA KEV catalog, indicating no confirmed public exploitation at the time of the advisory.