Threat Intelligence Database

Kysely versions from 0.26.0 up to 0.28.16 contain a path traversal vulnerability in the DefaultQueryCompiler.visitJSONPathLeg function. This flaw allows attacker-controlled input to manipulate JSON-path metacharacters, enabling traversal beyond intended JSON keys. Consequently, attackers can read and, in update statements, write to JSON sub-fields outside the developer's intended scope across MySQL, PostgreSQL, and SQLite databases. The vulnerability is fixed in version 0.28.

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.

HighVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-33468#cwe-89

Kysely is a type-safe TypeScript SQL query builder. In versions 0.28.12 and 0.28.13, the `sanitizeStringLiteral` method in Kysely's query compiler escapes single quotes (`'` → `''`) but does not escape backslashes. On MySQL with the default `BACKSLASH_ESCAPES` SQL mode, an attacker can inject a backslash before a single quote to neutralize the escaping, breaking out of the JSON path string literal and injecting arbitrary SQL. Version 0.28.14 fixes the issue.

HighVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-33442#cwe-89

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.

HighVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-32763#cwe-89