{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65980 exists.","fix":"No fix has been published for CVE-2026-65980 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-65980 is a high-severity SQL injection vulnerability in chartbrew, published on 21 Sep 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-65980 and fix it if it is affected.\n\nWhat it is: CVE-2026-65980 is a high-severity SQL injection vulnerability in chartbrew, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65980 exists.\n\nAffected product: chartbrew. 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-65980/ (Markdown: https://insights.sbomify.com/CVE-2026-65980/index.md)","id":"CVE-2026-65980","markdown":"https://insights.sbomify.com/CVE-2026-65980/index.md","name":"CVE-2026-65980","record":{"aliases":["GHSA-5jgv-45cw-hc53"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Chartbrew web application","requires_auth":"none","summary":"Attackers can execute arbitrary SQL on ClickHouse databases via public dashboards, leading to data disclosure or internal network access.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.9,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, Chartbrew's ClickHouse protocol in server/sources/plugins/clickhouse/clickhouse.protocol.js calls applySqlVariables() from server/sources/shared/sql/sql.variables.js without enabling the escapeBackslash option. For a ClickHouse-backed chart with variable binding, an attacker can supply a backslash before a quote so quote doubling does not keep the value within its intended SQL string literal. Public dashboards can expose this path without authentication, and successful exploitation can execute arbitrary ClickHouse SQL to disclose data or, when the database configuration permits, access files or internal network resources. This issue is fixed in version 5.2.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Chartbrew: SQL Injection via Missing Backslash Escaping in ClickHouse Variable Substitution","id":"CVE-2026-65980","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Coturn: MOBILITY-TICKET session-resume authorization bypass allows cross-user TURN allocation takeover","id":"CVE-2026-65981"},"packages":[],"prev":{"headline":"OpenEXR: Out-of-bounds read in HTJ2K decoder from unvalidated chunk header length (PLEN)","id":"CVE-2026-65979"},"products":["chartbrew"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["chartbrew"]},"summary":"Attackers can execute arbitrary SQL on ClickHouse databases via public dashboards, leading to data disclosure or internal network access.","url":"https://insights.sbomify.com/CVE-2026-65980/"}