{"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-27574 exists.","fix":"Upgrade @oneuptime/common to 10.0.0 or later.","what":"CVE-2026-27574 is a critical code injection vulnerability in oneuptime, published on 21 Feb 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-27574 and fix it if it is affected.\n\nWhat it is: CVE-2026-27574 is a critical code injection vulnerability in oneuptime, published on 21 Feb 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-27574 exists.\n\nAffected packages and fixed versions:\n- @oneuptime/common (npm): affected all versions; fixed in 10.0.0\n- @oneuptime/common (npm): affected all versions; fixed in 10.0.0\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-27574/ (Markdown: https://insights.sbomify.com/CVE-2026-27574/index.md)","id":"CVE-2026-27574","markdown":"https://insights.sbomify.com/CVE-2026-27574/index.md","name":"CVE-2026-27574","record":{"aliases":["GHSA-v264-xqh4-9xmm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"OneUptime monitoring platform","requires_auth":"low_privilege","summary":"An attacker can execute arbitrary code and compromise the cluster by exploiting a sandbox escape in the custom JavaScript monitor feature.","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-94","name":"Improper Control of Generation of Code"}],"description":"OneUptime is a solution for monitoring and managing online services. In versions 9.5.13 and below, custom JavaScript monitor feature uses Node.js's node:vm module (explicitly documented as not a security mechanism) to execute user-supplied code, allowing trivial sandbox escape via a well-known one-liner that grants full access to the underlying process. Because the probe runs with host networking and holds all cluster credentials (ONEUPTIME_SECRET, DATABASE_PASSWORD, REDIS_PASSWORD, CLICKHOUSE_PASSWORD) in its environment variables, and monitor creation is available to the lowest role (ProjectMember) with open registration enabled by default, any anonymous user can achieve full cluster compromise in about 30 seconds. This issue has been fixed in version 10.0.5.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-02-21","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-02-21T16:06:04Z","kind":"github_poc","ref":"https://github.com/mbanyamer/CVE-2026-27574-OneUptime-RCE","stars":1,"title":null}],"tier":"weaponised"},"has_fix":true,"headline":"OneUptime: node:vm sandbox escape in probe allows any project member to achieve RCE","id":"CVE-2026-27574","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":"Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change","id":"CVE-2026-27575"},"packages":[{"ecosystem":"npm","fixed":["10.0.0"],"introduced":["0"],"last_affected":[],"package":"@oneuptime/common","purl":null,"source":"GHSA-v264-xqh4-9xmm"},{"ecosystem":"npm","fixed":["10.0.0"],"introduced":["0"],"last_affected":[],"package":"@oneuptime/common","purl":"pkg:npm/%40oneuptime/common","source":"GHSA-v264-xqh4-9xmm"}],"prev":{"headline":"Further research determined the situation described is not a vulnerability.","id":"CVE-2026-27573"},"products":["oneuptime"],"published":"2026-02-21","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 Synthetic Monitor RCE via exposed Playwright browser object","id":"CVE-2026-30957","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-24","vendors":["OneUptime"]},"summary":"An attacker can execute arbitrary code and compromise the cluster by exploiting a sandbox escape in the custom JavaScript monitor feature.","url":"https://insights.sbomify.com/CVE-2026-27574/"}