# CVE-2026-45102: OneUptime sandbox escape in VMRunner leading to RCE

Source: https://junglewise.ai/threats/cve-2026-45102-oneuptime-sandbox-escape-in-vmrunner-leading-to-rce  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-27. Updated: 2026-05-27  
License: CC BY 4.0 with a link back

CVE-2026-45102 · Severity: critical · CVSS 9.9 · Published 2026-05-27

OneUptime is an open-source platform used for monitoring and observability of IT infrastructure. A security flaw in its code execution engine allows users with basic dashboard access to bypass security restrictions and run unauthorized commands on the underlying server. This could lead to a complete system takeover, theft of sensitive configuration data, or disruption of monitoring services.

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

## Quick answers

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

**How severe is CVE-2026-45102?** Critical severity, with a CVSS score of 9.9, published 27 May 2026.

**Which products and versions are affected?** OneUptime < 10.0.98.

**Is there a fix for CVE-2026-45102?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-45102 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-45102?** 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.

## Technical details

OneUptime is vulnerable to a sandbox escape leading to Remote Code Execution (RCE). The application utilized the Node.js 'vm' module as a security boundary for executing user-provided Playwright code in Synthetic Monitors. Because the 'vm' module is not a secure isolation primitive, an attacker can use techniques involving infinite recursion and error objects to access the host's global object and prototype chain. By exploiting this escape, a user with low-level project permissions can execute arbitrary shell commands on the host server. The issue is resolved in version 10.0.98 by migrating to a more secure isolation method.

## Affected products

- OneUptime OneUptime < 10.0.98

## Timeline

- 2026-05-07: advisory: GitHub Security Advisory published
- 2026-05-27: disclosed: CVE published to NVD

## References

- [https://github.com/OneUptime/oneuptime/security/advisories/GHSA-g9cp-35m2-fjv6](https://github.com/OneUptime/oneuptime/security/advisories/GHSA-g9cp-35m2-fjv6)

## Related threats

- [OneUptime authorization bypass in Kubernetes cluster operations](https://junglewise.ai/threats/cve-2026-112047-oneuptime-14-0-2-before-14-0-69-contains-an-incorrect)
- [OneUptime webhook SSRF via IPv4-mapped IPv6 addresses](https://junglewise.ai/threats/cve-2026-80350-oneuptime-webhook-ssrf-via-ipv4-mapped-ipv6-addresses)
- [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)