{"answers":{"affected":"2 open source packages ship an affected version, including oneuptime. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32306 exists.","fix":"Upgrade oneuptime to 10.0.23 or later.","what":"CVE-2026-32306 is a critical SQL injection vulnerability in oneuptime, published on 12 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-32306 and fix it if it is affected.\n\nWhat it is: CVE-2026-32306 is a critical SQL injection vulnerability in oneuptime, published on 12 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-32306 exists.\n\nAffected packages and fixed versions:\n- oneuptime (npm): affected all versions; fixed in 10.0.23\n- oneuptime (npm): affected all versions; fixed in 10.0.23\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-32306/ (Markdown: https://insights.sbomify.com/CVE-2026-32306/index.md)","id":"CVE-2026-32306","markdown":"https://insights.sbomify.com/CVE-2026-32306/index.md","name":"CVE-2026-32306","record":{"aliases":["GHSA-p5g2-jm85-8g35"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"OneUptime monitoring platform","requires_auth":"low_privilege","summary":"Authenticated users can inject SQL into ClickHouse queries via telemetry API parameters, allowing data theft, modification, and potential code execution.","user_interaction":"not_required","vuln_class":"sql_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-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"OneUptime is a solution for monitoring and managing online services. Prior to 10.0.23, the telemetry aggregation API accepts user-controlled aggregationType, aggregateColumnName, and aggregationTimestampColumnName parameters and interpolates them directly into ClickHouse SQL queries via the .append() method (documented as \"trusted SQL\"). There is no allowlist, no parameterized query binding, and no input validation. An authenticated user can inject arbitrary SQL into ClickHouse, enabling full database read (including telemetry data from all tenants), data modification, and potential remote code execution via ClickHouse table functions. This vulnerability is fixed in 10.0.23.","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 ClickHouse SQL Injection via Aggregate Query Parameters","id":"CVE-2026-32306","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"OneUptime: Stored XSS via Mermaid Diagram Rendering (securityLevel: \"loose\")","id":"CVE-2026-32308"},"packages":[{"ecosystem":"npm","fixed":["10.0.23"],"introduced":["0"],"last_affected":[],"package":"oneuptime","purl":null,"source":"GHSA-p5g2-jm85-8g35"},{"ecosystem":"npm","fixed":["10.0.23"],"introduced":["0"],"last_affected":[],"package":"oneuptime","purl":"pkg:npm/oneuptime","source":"GHSA-p5g2-jm85-8g35"}],"prev":{"headline":"Traefik mTLS bypass via fragmented ClientHello SNI extraction failure","id":"CVE-2026-32305"},"products":["oneuptime"],"published":"2026-03-12","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 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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-14","vendors":["OneUptime"]},"summary":"Authenticated users can inject SQL into ClickHouse queries via telemetry API parameters, allowing data theft, modification, and potential code execution.","url":"https://insights.sbomify.com/CVE-2026-32306/"}