Database/AI/ML frameworks & serving
Ray (GCS Redis credential handling / logging): When the Redis password is passed on the Ray command line it gets
Impact
When the Redis password is passed on the Ray command line it gets written into standard logs. Anyone who can read those logs - a log aggregator, a sidecar, a co-tenant with pod-log RBAC - recovers the password to the Global Control Store, which is the cluster's single source of truth for actor placement and job state. From there they can read or tamper with every tenant's workload metadata.
Who can reach it
A local or in-cluster reader of Ray's log output who also has network reach to the Redis instance. Requires that Redis auth is enabled and the password was supplied as an argument.
What to do
Upgrade Ray to 2.43.0 or later, then rotate the Redis password - the upgrade stops new leakage but does nothing about passwords already sitting in retained logs. Purge or re-key any log archives that captured the old value.
References
Related entries
- KServe ModelMesh: Group-writable `/etc/passwd` in the container imageCVE-2025-57852 · KServe ModelMeshMedium
- NVIDIA OpenShell: tunnels opened before a policy reload keep running under the old network policyCVE-2026-100970 · NVIDIA OpenShell for Linux (network policy hot-reload)Medium
- NVIDIA OpenShell: nonstandard HTTP methods bypass L7 policy on CONNECT tunnelsCVE-2026-100973 · NVIDIA OpenShell for Linux (L7 policy for HTTP CONNECT tunnels)Medium
- NVIDIA OpenShell: gateway accepts any sandbox host key, enabling machine-in-the-middleCVE-2026-100978 · NVIDIA OpenShell for Linux (gateway-to-sandbox transport)Medium
- NVIDIA OpenShell: HTTP request smuggling past the L7 REST proxy's policy checksCVE-2026-100981 · NVIDIA OpenShell for Linux (L7 REST proxy)Medium
- Jupyter Server: login `next` parameter allows redirect to an arbitrary external hostCVE-2025-61669 · Jupyter Server (LoginFormHandler redirect validation)Medium
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.