# CVE-2026-32763: SQL Injection via unsanitized JSON path keys when ignoring/silencing compilation errors or using `Kysely<any>`.

> Attackers can inject arbitrary SQL via unsanitized JSON path keys in Kysely, potentially leading to data theft or modification.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Mar 2026
- **Updated:** 21 Mar 2026
- **Also known as:** GHSA-wmrf-hv6w-mr66, MINI-gxqc-96r5-6j9x, MINI-h72c-jg4j-fcr3

## What is CVE-2026-32763?

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.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-32763?

2 open source packages ship an affected version, including kysely. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kysely` | npm | From 0.26.0 | 0.28.12 |
| `kysely` | npm | From 0.26.0 | 0.28.12 |

Products: Kysely Kysely.

## How do I fix CVE-2026-32763?

Upgrade kysely to 0.28.12 or later.

## Is CVE-2026-32763 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32763 exists.

## Other vulnerabilities in kysely-org kysely

- [CVE-2026-33442](https://insights.sbomify.com/CVE-2026-33442/): Kysely has a MySQL SQL Injection via Backslash Escape Bypass in non-type-safe usage of JSON path keys. (high 8.1)
- [CVE-2026-33468](https://insights.sbomify.com/CVE-2026-33468/): 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 (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32763 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32763 exists.

Affected packages and fixed versions:
- kysely (npm): affected from 0.26.0; fixed in 0.28.12
- kysely (npm): affected from 0.26.0; fixed in 0.28.12

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32763/ (Markdown: https://insights.sbomify.com/CVE-2026-32763/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32763
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32763
- OSV: https://osv.dev/vulnerability/CVE-2026-32763

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32763/
Summaries are generated and may contain mistakes; the official description above is the record.