Database/AI/ML frameworks & serving
Ray (dashboard /static/ file handler): Path traversal under the dashboard's /static/ route lets an unauthenticated
Impact
Path traversal under the dashboard's /static/ route lets an unauthenticated caller read any file the Ray process can open. On a GPU head node that typically means cloud instance credentials, kubeconfigs, SSH keys and other tenants' checkpoint paths - enough to pivot into the rest of the cluster. Part of the same 2023 Ray CVE cluster as the ShadowRay job-submission bug.
Who can reach it
Anyone who can issue HTTP requests to the Ray dashboard port (8265). No authentication required.
What to do
Upgrade Ray to 2.8.1 or later and restart the head node. Because the dashboard has no authentication by design in these versions, also restrict port 8265 with a NetworkPolicy or firewall and rotate any credential files that lived on the head node while it was exposed.
References
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.