Live › vulnerability › CVE-2026-112047
Go to dashboardOneUptime 14.0.2 before 14.0.69 checks permissions at the project level instead of per cluster. An authenticated project member can use its AI agent features to read agent RBAC permissions, disconnect agents, approve kubectl changes, or run commands on clusters they should not reach.
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 self-hosted OneUptime in the affected range with AI agent and kubectl plan features connected to Kubernetes clusters are exposed. The exposure depends on users who are project members with access to some clusters but not others. Deployments on versions or later, or without the agent and kubectl features in use, have less reason to worry; the sources do not say more.
14.0.69No product ranges from the sources yet.
14.0.2 up to but not including 14.0.69.14.0.69 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
OneUptime 14.0.2 before 14.0.69 contains an incorrect authorization vulnerability that allows authenticated project members to act on clusters outside their scope by exploiting project-wide permission checks. Attackers can call the AI access test, agent reset, kubectl plan approval and incident AI conversation features to learn agent RBAC permissions, disconnect agents, approve kubectl changes, or run commands on unauthorized resources.
This page as .md · .json · in your agent: get_signal("CVE-2026-112047")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.