Database/AI/ML frameworks & serving
Ray (job submission API): Unauthenticated RCE — the Jobs API accepts arbitrary code by design
Impact
Unauthenticated RCE — the Jobs API accepts arbitrary code by design
Who can reach it
Unauthenticated network to the Ray dashboard/Jobs API (default 8265)
What to do
**No patch — vendor disputes it.** The only remediation is network isolation and an auth proxy. Exploited in the wild against GPU clusters; a neocloud must never let 8265 reach a tenant or public network
Fleet impact
How widespread
Very common - Ray is the default distributed-compute layer for RL, tuning and batch inference on GPU clusters; ~230k exposed instances observed
Cost to remediate
node-drain + network re-architecture - there is no vendor patch (Anyscale calls it intended behavior), so remediation means putting auth in front of every dashboard/Jobs API and restarting every Ray cluster in the fleet
Why it hits the whole fleet
The Jobs API has no authorization: anyone who can reach the dashboard submits arbitrary code to the whole cluster, so one exposed head node hands over every GPU and every dataset attached to it
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.