{"answers":{"affected":"2 open source packages ship an affected version, including @oneuptime/common. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30957 exists.","fix":"Upgrade @oneuptime/common to 10.0.21 or later.","what":"CVE-2026-30957 is a critical code injection vulnerability in oneuptime, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-30957 and fix it if it is affected.\n\nWhat it is: CVE-2026-30957 is a critical code injection vulnerability in oneuptime, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30957 exists.\n\nAffected packages and fixed versions:\n- @oneuptime/common (npm): affected all versions; fixed in 10.0.21\n- @oneuptime/common (npm): affected all versions; fixed in 10.0.21\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-30957/ (Markdown: https://insights.sbomify.com/CVE-2026-30957/index.md)","id":"CVE-2026-30957","markdown":"https://insights.sbomify.com/CVE-2026-30957/index.md","name":"CVE-2026-30957","record":{"aliases":["GHSA-jw8q-gjvg-8w4q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"OneUptime monitoring platform","requires_auth":"low_privilege","summary":"A low-privileged user can execute arbitrary commands on the probe server by injecting code into Synthetic Monitors that accesses exposed Playwright objects.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"oneuptime","vendor":"hackerbay"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-749","name":"Exposed Dangerous Method or Function"}],"description":"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'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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"OneUptime Synthetic Monitor RCE via exposed Playwright browser object","id":"CVE-2026-30957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"OneUptime: Path Traversal — Arbitrary File Read (No Auth)","id":"CVE-2026-30958"},"packages":[{"ecosystem":"npm","fixed":["10.0.21"],"introduced":["0"],"last_affected":[],"package":"@oneuptime/common","purl":null,"source":"GHSA-jw8q-gjvg-8w4q"},{"ecosystem":"npm","fixed":["10.0.21"],"introduced":["0"],"last_affected":[],"package":"@oneuptime/common","purl":"pkg:npm/%40oneuptime/common","source":"GHSA-jw8q-gjvg-8w4q"}],"prev":{"headline":"OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header","id":"CVE-2026-30956"},"products":["oneuptime"],"published":"2026-03-10","related":[{"cvss_score":10,"headline":"Code injection in oneuptime","id":"CVE-2026-33396","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":10,"headline":"OneUptime ClickHouse SQL Injection via Aggregate Query Parameters","id":"CVE-2026-32306","kev_date_added":null,"published":"2026-03-12"},{"cvss_score":10,"headline":"OneUptime has authorization bypass via client‑controlled is-multi-tenant-query header","id":"CVE-2026-30956","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":10,"headline":"OneUptime Affected by Unsandboxed Code Execution in Probe Allows Any Project Member to Achieve RCE","id":"CVE-2026-30887","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":10,"headline":"OneUptime Synthetic Monitor RCE via exposed Playwright browser object","id":"CVE-2026-30921","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":10,"headline":"OneUptime: OS Command Injection in Probe NetworkPathMonitor via unsanitized destination in traceroute exec()","id":"CVE-2026-27728","kev_date_added":null,"published":"2026-02-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-10","vendors":["OneUptime"]},"summary":"A low-privileged user can execute arbitrary commands on the probe server by injecting code into Synthetic Monitors that accesses exposed Playwright objects.","url":"https://insights.sbomify.com/CVE-2026-30957/"}