{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35053 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-35053 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35053 is a critical missing authorization vulnerability in oneuptime, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35053 and fix it if it is affected.\n\nWhat it is: CVE-2026-35053 is a critical missing authorization vulnerability in oneuptime, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-35053 in the wild and no public exploit code.\n\nAffected product: oneuptime. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-35053/ (Markdown: https://insights.sbomify.com/CVE-2026-35053/index.md)","id":"CVE-2026-35053","markdown":"https://insights.sbomify.com/CVE-2026-35053/index.md","name":"CVE-2026-35053","record":{"aliases":["GHSA-6c3w-7xg4-4cf7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"OneUptime monitoring platform","requires_auth":"none","summary":"Unauthenticated attackers can trigger arbitrary workflow execution in OneUptime, leading to JavaScript code execution and data manipulation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"oneuptime","vendor":"hackerbay"}],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"OneUptime is an open-source monitoring and observability platform. Prior to version 10.0.42, the Worker service's ManualAPI exposes workflow execution endpoints (GET /workflow/manual/run/:workflowId and POST /workflow/manual/run/:workflowId) without any authentication middleware. An attacker who can obtain or guess a workflow ID can trigger arbitrary workflow execution with attacker-controlled input data, enabling JavaScript code execution, notification abuse, and data manipulation. This issue has been patched in version 10.0.42.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"OneUptime: Unauthenticated Workflow Execution via ManualAPI","id":"CVE-2026-35053","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"XenForo Stored Cross-Site Scripting via BB Code Rendering","id":"CVE-2026-35054"},"packages":[],"prev":{"headline":"D-Tale affected by Remote Code Execution through redis/shelf storage","id":"CVE-2026-35052"},"products":["oneuptime"],"published":"2026-04-02","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":"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-03","vendors":["OneUptime"]},"summary":"Unauthenticated attackers can trigger arbitrary workflow execution in OneUptime, leading to JavaScript code execution and data manipulation.","url":"https://insights.sbomify.com/CVE-2026-35053/"}