<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 17 Oct 2026 18:59:34 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-277661</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-277661</link>
      <description>EUVD-2026-277661</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-277661</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33442</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33442</link>
      <description>&lt;p&gt;Kysely is a type-safe TypeScript SQL query builder. In versions 0.28.12 and 0.28.13, the `sanitizeStringLiteral` method in Kysely&amp;#39;s query compiler escapes single quotes (`&amp;#39;` → `&amp;#39;&amp;#39;`) 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Kysely is a type-safe TypeScript SQL query builder. In versions 0.28.12 and 0.28.13, the `sanitizeStringLiteral` method in Kysely&amp;#39;s query compiler escapes single quotes (`&amp;#39;` → `&amp;#39;&amp;#39;`) 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33442</guid>
    </item>
    <item>
      <title>GHSA-fr9j-6mvq-frcv — Kysely has a MySQL SQL Injection via Backslash Escape Bypass in non-type-safe usage of JSON path keys.</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fr9j-6mvq-frcv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: kysely&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `sanitizeStringLiteral` method in Kysely&amp;#39;s query compiler escapes single quotes (`&amp;#39;` → `&amp;#39;&amp;#39;`) 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.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;When a user calls `.key(value)` on a JSON path builder, the value flows through:&lt;/p&gt;
&lt;p&gt;1. `JSONPathBuilder.key(key)` at `src/query-builder/json-path-builder.ts:166` stores the key as a `JSONPathLegNode` with type `&amp;#39;Member&amp;#39;`.&lt;/p&gt;
&lt;p&gt;2. During compilation, `DefaultQueryCompiler.visitJSONPath()` at `src/query-compiler/default-query-compiler.ts:1609` wraps the full path in single quotes (`&amp;#39;$...&amp;#39;`).&lt;/p&gt;
&lt;p&gt;3. `DefaultQueryCompiler.visitJSONPathLeg()` at `src/query-compiler/default-query-compiler.ts:1623` calls `sanitizeStringLiteral(node.value)` for string values (line 1630).&lt;/p&gt;
&lt;p&gt;4. `sanitizeStringLiteral()` at `src/query-compiler/default-query-compiler.ts:1819-1821` only doubles single quotes:&lt;/p&gt;
&lt;p&gt;```typescript
// src/query-compiler/default-query-compiler.ts:121
const LIT_WRAP_REGEX = /&amp;#39;/g&lt;/p&gt;
&lt;p&gt;// src/query-compiler/default-query-compiler.ts:1819-1821
protected sanitizeStringLiteral(value: string): string {
  return value.replace(LIT_WRAP_REGEX, &amp;#34;&amp;#39;&amp;#39;&amp;#34;)
}
```&lt;/p&gt;
&lt;p&gt;The `MysqlQueryCompiler` does not override `sanitizeStringLiteral` — it only overrides `sanitizeIdentifier` for backtick escaping.&lt;/p&gt;
&lt;p&gt;**The bypass mechanism:**&lt;/p&gt;
&lt;p&gt;In MySQL&amp;#39;s default `BACKSLAS…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: kysely&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `sanitizeStringLiteral` method in Kysely&amp;#39;s query compiler escapes single quotes (`&amp;#39;` → `&amp;#39;&amp;#39;`) 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.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;When a user calls `.key(value)` on a JSON path builder, the value flows through:&lt;/p&gt;
&lt;p&gt;1. `JSONPathBuilder.key(key)` at `src/query-builder/json-path-builder.ts:166` stores the key as a `JSONPathLegNode` with type `&amp;#39;Member&amp;#39;`.&lt;/p&gt;
&lt;p&gt;2. During compilation, `DefaultQueryCompiler.visitJSONPath()` at `src/query-compiler/default-query-compiler.ts:1609` wraps the full path in single quotes (`&amp;#39;$...&amp;#39;`).&lt;/p&gt;
&lt;p&gt;3. `DefaultQueryCompiler.visitJSONPathLeg()` at `src/query-compiler/default-query-compiler.ts:1623` calls `sanitizeStringLiteral(node.value)` for string values (line 1630).&lt;/p&gt;
&lt;p&gt;4. `sanitizeStringLiteral()` at `src/query-compiler/default-query-compiler.ts:1819-1821` only doubles single quotes:&lt;/p&gt;
&lt;p&gt;```typescript
// src/query-compiler/default-query-compiler.ts:121
const LIT_WRAP_REGEX = /&amp;#39;/g&lt;/p&gt;
&lt;p&gt;// src/query-compiler/default-query-compiler.ts:1819-1821
protected sanitizeStringLiteral(value: string): string {
  return value.replace(LIT_WRAP_REGEX, &amp;#34;&amp;#39;&amp;#39;&amp;#34;)
}
```&lt;/p&gt;
&lt;p&gt;The `MysqlQueryCompiler` does not override `sanitizeStringLiteral` — it only overrides `sanitizeIdentifier` for backtick escaping.&lt;/p&gt;
&lt;p&gt;**The bypass mechanism:**&lt;/p&gt;
&lt;p&gt;In MySQL&amp;#39;s default `BACKSLAS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fr9j-6mvq-frcv</guid>
    </item>
  </channel>
</rss>
