Vulnerability in kysely (CVE-2026-44635)
Summary
Vulnerability in kysely (CVE-2026-44635). Confidential information can be exposed externally. Exploitable via DefaultQueryCompiler.visitJSONPathLeg. Mitigation: upgrade to 0.28.17 or later.
Original description
The description as published by the source.
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, '->$').key(input) or .at(input) — including type-safe code where the JSON column is shaped like Record 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 ->$/->>$, and SQLite. This vulnerability is fixed in 0.28.17.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44635 has been found in kysely.
Attackers can target a specific entry point like DefaultQueryCompiler.visitJSONPathLeg over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade kysely to 0.28.17 or later.
If unsure, ask your IT team or search "kysely CVE-2026-44635" on the vendor's site.
CVE-2026-44635 (kysely) — CWE-1284 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DefaultQueryCompiler.visitJSONPathLeg / kysely / master / sanitizeStringLiteral
Patched: 0.28.17 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1284) exists in kysely. Attackers reach the vulnerable code path via DefaultQueryCompiler.visitJSONPathLeg without authentication.
Check the vendor advisory for the affected versions of kysely. Attack surface: DefaultQueryCompiler.visitJSONPathLeg / kysely / master / sanitizeStringLiteral.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 0.28.17.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'kysely' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'kysely' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
kyselyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade kysely to 0.28.17ステージング環境で 0.28.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com