{"answers":{"affected":"2 open source packages ship an affected version, including kysely. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32763 exists.","fix":"Upgrade kysely to 0.28.12 or later.","what":"CVE-2026-32763 is a high-severity SQL injection vulnerability in kysely-org kysely, published on 19 Mar 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-32763 and fix it if it is affected.\n\nWhat it is: CVE-2026-32763 is a high-severity SQL injection vulnerability in kysely-org kysely, published on 19 Mar 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-32763 exists.\n\nAffected packages and fixed versions:\n- kysely (npm): affected from 0.26.0; fixed in 0.28.12\n- kysely (npm): affected from 0.26.0; fixed in 0.28.12\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-32763/ (Markdown: https://insights.sbomify.com/CVE-2026-32763/index.md)","id":"CVE-2026-32763","markdown":"https://insights.sbomify.com/CVE-2026-32763/index.md","name":"CVE-2026-32763","record":{"aliases":["GHSA-wmrf-hv6w-mr66","MINI-gxqc-96r5-6j9x","MINI-h72c-jg4j-fcr3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"TypeScript SQL query builder","requires_auth":"none","summary":"Attackers can inject arbitrary SQL via unsanitized JSON path keys in Kysely, potentially leading to data theft or modification.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kysely","vendor":"kysely"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Kysely is a type-safe TypeScript SQL query builder. Versions up to and including 0.28.11 has a SQL injection vulnerability in JSON path compilation for MySQL and SQLite dialects. The `visitJSONPathLeg()` function appends user-controlled values from `.key()` and `.at()` directly into single-quoted JSON path string literals (`'$.key'`) without escaping single quotes. An attacker can break out of the JSON path string context and inject arbitrary SQL. This is inconsistent with `sanitizeIdentifier()`, which properly doubles delimiter characters for identifiers — both are non-parameterizable SQL constructs requiring manual escaping, but only identifiers are protected. Version 0.28.12 fixes the issue.","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":"SQL Injection via unsanitized JSON path keys when ignoring/silencing compilation errors or using `Kysely\u003cany\u003e`.","id":"CVE-2026-32763","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"This repository is no longer public.","id":"CVE-2026-32764"},"packages":[{"ecosystem":"npm","fixed":["0.28.12"],"introduced":["0.26.0"],"last_affected":[],"package":"kysely","purl":null,"source":"GHSA-wmrf-hv6w-mr66"},{"ecosystem":"npm","fixed":["0.28.12"],"introduced":["0.26.0"],"last_affected":[],"package":"kysely","purl":"pkg:npm/kysely","source":"GHSA-wmrf-hv6w-mr66"}],"prev":{"headline":"Rack: Forwarded Header semicolon injection enables Host and Scheme spoofing","id":"CVE-2026-32762"},"products":["kysely"],"published":"2026-03-19","related":[{"cvss_score":8.1,"headline":"Kysely has a MySQL SQL Injection via Backslash Escape Bypass in non-type-safe usage of JSON path keys.","id":"CVE-2026-33442","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.1,"headline":"Kysely has a MySQL SQL Injection via Insufficient Backslash Escaping in `sql.lit(string)` usage or similar methods that append string literal values into the compiled SQL strings","id":"CVE-2026-33468","kev_date_added":null,"published":"2026-03-26"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-21","vendors":["kysely-org"]},"summary":"Attackers can inject arbitrary SQL via unsanitized JSON path keys in Kysely, potentially leading to data theft or modification.","url":"https://insights.sbomify.com/CVE-2026-32763/"}