# CVE-2026-112047: OneUptime authorization bypass in Kubernetes cluster operations

Source: https://junglewise.ai/threats/cve-2026-112047-oneuptime-14-0-2-before-14-0-69-contains-an-incorrect  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-18. Updated: 2026-10-18  
License: CC BY 4.0 with a link back

CVE-2026-112047 · Severity: medium · CVSS 5.4 · Published 2026-10-18

OneUptime is a monitoring and incident management platform that manages Kubernetes clusters and infrastructure agents. Authenticated project members can exploit insufficient authorization checks to perform restricted operations on clusters they should not have access to, including approving infrastructure changes and running commands on unauthorized resources, potentially leading to service disruption or unauthorized cluster access.

Technologies: [OneUptime](https://junglewise.ai/threats/technologies/oneuptime). Vendors: [OneUptime](https://junglewise.ai/threats/vendors/oneuptime).

## Quick answers

**Is CVE-2026-112047 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-112047 being exploited in the wild.

**How severe is CVE-2026-112047?** Medium severity, with a CVSS score of 5.4, published 18 October 2026.

**Which products and versions are affected?** OneUptime 14.0.2 before 14.0.69.

**Is there a fix for CVE-2026-112047?** Yes: fixed in 14.0.69. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-112047 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-112047?** Check whether you run OneUptime at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 14.0.69

## Technical details

The vulnerability is an incorrect authorization flaw in OneUptime 14.0.2 through 14.0.68 where cluster-specific operations (AI access test, agent reset, kubectl plan approval, incident AI conversation) check only project-wide permissions rather than cluster-scoped permissions. An authenticated project member can call these APIs to interact with clusters outside their authorization scope, learn agent RBAC permissions, disconnect agents, approve kubectl changes, or execute commands on unauthorized resources.

## Affected products

- OneUptime OneUptime 14.0.2 before 14.0.69

## Timeline

- 2026-10-18: disclosed

## References

- [https://github.com/OneUptime/oneuptime/blob/14.0.68/packages/Common/Server/API/KubernetesClusterAiAccessAPI.ts](https://github.com/OneUptime/oneuptime/blob/14.0.68/packages/Common/Server/API/KubernetesClusterAiAccessAPI.ts)
- [https://github.com/OneUptime/oneuptime/commit/264e1ba13149cbd4c80cb22f2177b405886b0452](https://github.com/OneUptime/oneuptime/commit/264e1ba13149cbd4c80cb22f2177b405886b0452)

## Related threats

- [OneUptime webhook SSRF via IPv4-mapped IPv6 addresses](https://junglewise.ai/threats/cve-2026-80350-oneuptime-webhook-ssrf-via-ipv4-mapped-ipv6-addresses)
- [OneUptime sandbox escape in VMRunner leading to RCE](https://junglewise.ai/threats/cve-2026-45102-oneuptime-sandbox-escape-in-vmrunner-leading-to-rce)
- [OneUptime missing authentication in Worker ManualAPI workflow execution](https://junglewise.ai/threats/cve-2026-35053-oneuptime-missing-authentication-in-worker-manualapi-workflow)
- [OneUptime SAML SSO authentication bypass via identity injection](https://junglewise.ai/threats/cve-2026-34840-oneuptime-saml-sso-authentication-bypass-via-identity-injection)
- [OneUptime missing authorization in notification API endpoints](https://junglewise.ai/threats/cve-2026-34759-oneuptime-missing-authorization-in-notification-api-endpoints)