Live › vulnerability › CVE-2026-111671
Go to dashboardCube-studio, a Kubernetes-based machine learning platform, does not check ownership of notebook and inference service ids on its lifecycle endpoints. Any logged-in user can pass sequential ids to stop, reset, clear or redeploy other users' notebooks and services, taking production inference endpoints offline.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running Cube-studio with multiple authenticated users who share the platform, since the flaw lets one user act on another's notebooks and serving endpoints. Single-user deployments where every account belongs to the same trusted person are less exposed. unknown whether the sources say more about default configuration.
No product ranges from the sources yet.
2026.09.01view_notebook.py, view_inferenceserving.py and view_serving.py for ownership checks on lifecycle endpoints (unknown if the sources give a fixed version)2026.09.01Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Cube-studio through 2026.09.01 contains an insecure direct object reference vulnerability that allows authenticated users to stop, reset, clear or redeploy other users' notebooks and services by id. Attackers can pass sequential ids to lifecycle endpoints in view_notebook.py, view_inferenceserving.py and view_serving.py to delete pods and take production inference endpoints offline.
This page as .md · .json · in your agent: get_signal("CVE-2026-111671")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.