https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 17:52:57 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-275318 EUVD-2026-275318 https://cve.radiocsirt.org/vuln/euvd-2026-275318 https://cve.radiocsirt.org/vuln/fkie_cve-2026-30957 <p>OneUptime is a solution for monitoring and managing online services. Prior to 10.0.21, OneUptime Synthetic Monitors allow a low-privileged authenticated project user to execute arbitrary commands on the oneuptime-probe server/container. The root cause is that untrusted Synthetic Monitor code is executed inside Node&#39;s vm while live host-realm Playwright browser and page objects are exposed to it. A malicious user can call Playwright APIs on the injected browser object and cause the probe to spawn an attacker-controlled executable. This is a server-side remote code execution issue. It does not require a separate vm sandbox escape. This vulnerability is fixed in 10.0.21.</p> <p>OneUptime is a solution for monitoring and managing online services. Prior to 10.0.21, OneUptime Synthetic Monitors allow a low-privileged authenticated project user to execute arbitrary commands on the oneuptime-probe server/container. The root cause is that untrusted Synthetic Monitor code is executed inside Node&#39;s vm while live host-realm Playwright browser and page objects are exposed to it. A malicious user can call Playwright APIs on the injected browser object and cause the probe to spawn an attacker-controlled executable. This is a server-side remote code execution issue. It does not require a separate vm sandbox escape. This vulnerability is fixed in 10.0.21.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-30957 https://cve.radiocsirt.org/vuln/ghsa-jw8q-gjvg-8w4q <p><strong>Affected:</strong> npm: @oneuptime/common</p> <p>### Summary</p> <p>OneUptime Synthetic Monitors allow a low-privileged authenticated project user to execute arbitrary commands on the `oneuptime-probe` server/container.</p> <p>The root cause is that untrusted Synthetic Monitor code is executed inside Node&#39;s `vm` while live host-realm Playwright `browser` and `page` objects are exposed to it. A malicious user can call Playwright APIs on the injected `browser` object and cause the probe to spawn an attacker-controlled executable.</p> <p>This is a server-side remote code execution issue. It does not require a separate `vm` sandbox escape.</p> <p>## Details</p> <p>A normal project member can create or edit monitors and monitor tests:</p> <p>- `Monitor` access control: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/Common/Models/DatabaseModels/Monitor.ts#L45-L70 - `MonitorTest` access control: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/Common/Models/DatabaseModels/MonitorTest.ts#L27-L52</p> <p>The dashboard exposes a Playwright code editor for Synthetic Monitors and allows a user to queue a test run:</p> <p>- Synthetic Monitor editor: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/App/FeatureSet/Dashboard/src/Components/Form/Monitor/MonitorStep.tsx#L260-L289 - `Test Monitor` flow: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/App/FeatureSet/Dashboard/src/Components/Form/Monitor/MonitorTest.tsx#L69-L83</p> <p>For `MonitorType.S…</p> <p><strong>Affected:</strong> npm: @oneuptime/common</p> <p>### Summary</p> <p>OneUptime Synthetic Monitors allow a low-privileged authenticated project user to execute arbitrary commands on the `oneuptime-probe` server/container.</p> <p>The root cause is that untrusted Synthetic Monitor code is executed inside Node&#39;s `vm` while live host-realm Playwright `browser` and `page` objects are exposed to it. A malicious user can call Playwright APIs on the injected `browser` object and cause the probe to spawn an attacker-controlled executable.</p> <p>This is a server-side remote code execution issue. It does not require a separate `vm` sandbox escape.</p> <p>## Details</p> <p>A normal project member can create or edit monitors and monitor tests:</p> <p>- `Monitor` access control: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/Common/Models/DatabaseModels/Monitor.ts#L45-L70 - `MonitorTest` access control: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/Common/Models/DatabaseModels/MonitorTest.ts#L27-L52</p> <p>The dashboard exposes a Playwright code editor for Synthetic Monitors and allows a user to queue a test run:</p> <p>- Synthetic Monitor editor: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/App/FeatureSet/Dashboard/src/Components/Form/Monitor/MonitorStep.tsx#L260-L289 - `Test Monitor` flow: https://github.com/OneUptime/oneuptime/blob/707bfd62e721a2845ee05b87cb5d3c611bda2276/App/FeatureSet/Dashboard/src/Components/Form/Monitor/MonitorTest.tsx#L69-L83</p> <p>For `MonitorType.S…</p> https://cve.radiocsirt.org/vuln/ghsa-jw8q-gjvg-8w4q