{"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-33468 exists.","fix":"Upgrade kysely to 0.28.14 or later.","what":"CVE-2026-33468 is a high-severity SQL injection vulnerability in kysely-org kysely, published on 26 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-33468 and fix it if it is affected.\n\nWhat it is: CVE-2026-33468 is a high-severity SQL injection vulnerability in kysely-org kysely, published on 26 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-33468 exists.\n\nAffected packages and fixed versions:\n- kysely (npm): affected all versions; fixed in 0.28.14\n- kysely (npm): affected all versions; fixed in 0.28.14\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-33468/ (Markdown: https://insights.sbomify.com/CVE-2026-33468/index.md)","id":"CVE-2026-33468","markdown":"https://insights.sbomify.com/CVE-2026-33468/index.md","name":"CVE-2026-33468","record":{"aliases":["GHSA-8cpq-38p9-67gx","MINI-6459-9wcc-52w5","MINI-g84g-q97h-rv2x"],"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 insufficient backslash escaping in Kysely's MySQL dialect, 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.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/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":"Kysely is a type-safe TypeScript SQL query builder. Prior to version 0.28.14, Kysely's `DefaultQueryCompiler.sanitizeStringLiteral()` only escapes single quotes by doubling them (`'` → `''`) but does not escape backslashes. When used with the MySQL dialect (where `NO_BACKSLASH_ESCAPES` is OFF by default), an attacker can use a backslash to escape the trailing quote of a string literal, breaking out of the string context and injecting arbitrary SQL. This affects any code path that uses `ImmediateValueTransformer` to inline values — specifically `CreateIndexBuilder.where()` and `CreateViewBuilder.as()`. Version 0.28.14 contains a fix.","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":"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","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":"Authenticated Frigate users can read the full unredacted configuration via `/api/config/raw","id":"CVE-2026-33469"},"packages":[{"ecosystem":"npm","fixed":["0.28.14"],"introduced":["0"],"last_affected":[],"package":"kysely","purl":null,"source":"GHSA-8cpq-38p9-67gx"},{"ecosystem":"npm","fixed":["0.28.14"],"introduced":["0"],"last_affected":[],"package":"kysely","purl":"pkg:npm/kysely","source":"GHSA-8cpq-38p9-67gx"}],"prev":{"headline":"Improper Verification of Cryptographic Signature in Elastic Package Registry Leading to Package Integrity Bypass","id":"CVE-2026-33467"},"products":["kysely"],"published":"2026-03-26","related":[{"cvss_score":8.2,"headline":"SQL Injection via unsanitized JSON path keys when ignoring/silencing compilation errors or using `Kysely\u003cany\u003e`.","id":"CVE-2026-32763","kev_date_added":null,"published":"2026-03-19"},{"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"}],"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-26","vendors":["kysely-org"]},"summary":"Attackers can inject arbitrary SQL via insufficient backslash escaping in Kysely's MySQL dialect, potentially leading to data theft or modification.","url":"https://insights.sbomify.com/CVE-2026-33468/"}