CVE-2026-111671: Cube-studio through 2026.09.01 IDOR via Notebook and Serving Lifecycle Endpoints

Q: Who can exploit this issue?

An authenticated Cube-studio user can exploit it. The attacker needs the numeric ID of another user's notebook, service, or inference-serving object; sequential IDs can be passed to the affected lifecycle endpoints.

Q: What is the operational impact of a successful attack?

An attacker can stop, reset, clear, or redeploy other users' notebooks and services. The affected actions can delete pods and take production inference endpoints offline.

Q: Are unauthenticated deployments affected?

The described attack requires authentication, so an unauthenticated attacker is not described as able to exploit it directly. Any account with access to the affected lifecycle endpoints should be considered a potential attacker.

Q: How can I determine whether an instance is affected?

Cube-studio versions through 2026.09.01 are affected according to the available data. Review whether authenticated users can invoke notebook, inference-serving, or serving lifecycle actions against object IDs they do not own.

Published Oct 16, 2026

Updated

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 viewnotebook.py, viewinferenceserving.py and viewserving.py to delete pods and take production inference endpoints offline.

Affected Software

1 affected component

Cube-studio Cube-studio<=2026.09.01

Event History

Oct 16, 2026

CVE Published

via MITRE·05:39 PM

Data Sourced

via MITRE·05:39 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who can exploit this issue?

An authenticated Cube-studio user can exploit it. The attacker needs the numeric ID of another user's notebook, service, or inference-serving object; sequential IDs can be passed to the affected lifecycle endpoints.

What is the operational impact of a successful attack?

An attacker can stop, reset, clear, or redeploy other users' notebooks and services. The affected actions can delete pods and take production inference endpoints offline.

Are unauthenticated deployments affected?

The described attack requires authentication, so an unauthenticated attacker is not described as able to exploit it directly. Any account with access to the affected lifecycle endpoints should be considered a potential attacker.

How can I determine whether an instance is affected?

Cube-studio versions through 2026.09.01 are affected according to the available data. Review whether authenticated users can invoke notebook, inference-serving, or serving lifecycle actions against object IDs they do not own.

CVE-2026-111671: Cube-studio through 2026.09.01 IDOR via Notebook and Serving Lifecycle Endpoints

Affected Software

Event History

Frequently Asked Questions

Who can exploit this issue?

What is the operational impact of a successful attack?

Are unauthenticated deployments affected?

How can I determine whether an instance is affected?

Company

Resources

Contact

Frequently Asked Questions

Who can exploit this issue?

What is the operational impact of a successful attack?

Are unauthenticated deployments affected?

How can I determine whether an instance is affected?