<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T06:56:18.322273+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-44635</id>
    <title>fkie_cve-2026-44635</title>
    <updated>2026-10-02T06:56:18.358713+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Kysely is a type-safe TypeScript SQL query builder. From 0.26.0 to 0.28.16, DefaultQueryCompiler.visitJSONPathLeg does not escape JSON-path metacharacters (., [, ], *, **, ?). When attacker-controlled input flows into eb.ref(col, '-&gt;$').key(input) or .at(input) — including type-safe code where the JSON column is shaped like Record&lt;string, T&gt; so K extends string is the inferred type — every dot becomes a path-leg separator, letting an attacker traverse from the intended key into sibling and child fields the developer never meant to expose. The result is read access (and, in update statements, write access) to JSON sub-fields outside the intended scope across MySQL, PostgreSQL -&gt;$/-&gt;&gt;$, and SQLite. This vulnerability is fixed in 0.28.17.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-44635"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-pv5w-4p9q-p3v2</id>
    <title>GHSA-pv5w-4p9q-p3v2 — Kysely: JSON-path traversal injection via unsanitized path-leg metacharacters in `JSONPathBuilder.key()` / `.at()`</title>
    <updated>2026-10-02T06:56:18.359030+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: kysely</p>
<p>## Summary</p>
<p>Kysely 0.28.12 added a `sanitizeStringLiteral()` call inside `DefaultQueryCompiler.visitJSONPathLeg` (commit `0a602bf`, PR #1727) to fix CVE-2026-32763 (`GHSA-wmrf-hv6w-mr66`). The fix only doubles single quotes (`'` → `''`); it does **not** escape JSON-path metacharacters (`.`, `[`, `]`, `*`, `**`, `?`). When attacker-controlled input flows into `eb.ref(col, '-&gt;$').key(input)` or `.at(input)` — including type-safe code where the JSON column is shaped like `Record&lt;string, T&gt;` so `K extends string` is the inferred type — every dot becomes a path-leg separator, letting an attacker traverse from the intended key into sibling and child fields the developer never meant to expose. The result is read access (and, in update statements, write access) to JSON sub-fields outside the intended scope across MySQL, PostgreSQL `-&gt;$`/`-&gt;&gt;$`, and SQLite.</p>
<p>* Project: Kysely — TypeScript SQL query builder (npm `kysely`); affects MySQL, PostgreSQL `-&gt;$`/`-&gt;&gt;$`, and SQLite dialects.
* Source reviewed: `kysely-org/kysely` @ `master` (`73192e4`, version `0.28.16`).
* Deployed artefact validated: `kysely@0.28.16` from npm.
* Affected file(s):
  * `src/query-compiler/default-query-compiler.ts` (lines 1611–1639, 1821–1823)
  * `src/query-builder/json-path-builder.ts` (lines 93–196)
  * `src/dialect/mysql/mysql-query-compiler.ts` (overrides `sanitizeStringLiteral` but inherits the same behaviour for path legs — escapes `\` and `'`, nothing else)
* CWE: CWE-89 — Improper Neutralization of Sp…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-pv5w-4p9q-p3v2"/>
  </entry>
</feed>
