← Back
CVE-2026-44635
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.
AI summary snake-internal / snake-material-v2
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: ?/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 /
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.
❓ What is the problem
**A vulnerability** (CWE-1284) exists in kysely. Attackers reach the vulnerable code path via ``DefaultQueryCompiler.visitJSONPathLeg`` without authentication.
📍 Affected scope
kysely — . Attack surface: `DefaultQueryCompiler.visitJSONPathLeg` / `kysely` / `master` / `sanitizeStringLiteral`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.28.17**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade kysely to 0.28.17ステージング環境で 0.28.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
kysely
[{"type":"SEMVER","events":[{"introduced":"0.26.0"},{"fixed":"0.28.17"}]}]