CVE-2026-44635: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in kysely-org kysely
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.
AI Analysis
Technical Summary
Kysely, a type-safe TypeScript SQL query builder, has a vulnerability (CVE-2026-44635) in versions 0.26.0 through 0.28.16 where DefaultQueryCompiler.visitJSONPathLeg does not properly escape JSON-path metacharacters such as ., [, ], *, **, and ?. When attacker-controlled input is passed to eb.ref(col, '->$').key(input) or .at(input), each dot character is interpreted as a path-leg separator. This allows traversal from the intended JSON key into sibling and child fields that developers did not intend to expose. This results in unauthorized read access and, in update statements, write access to JSON sub-fields across MySQL, PostgreSQL, and SQLite databases. The issue is resolved in version 0.28.17.
Potential Impact
The vulnerability allows an attacker to bypass intended JSON key restrictions and access or modify JSON sub-fields outside the authorized scope. This can lead to unauthorized data disclosure and unauthorized data modification in affected databases. The impact is limited to JSON data fields accessed via the vulnerable Kysely versions. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
A fix is available in Kysely version 0.28.17. Users should upgrade to version 0.28.17 or later to remediate this vulnerability. Since this is a library vulnerability, applying the official patch by upgrading is the recommended mitigation. Patch status is confirmed by the vendor advisory stating the issue is fixed in 0.28.17.
CVE-2026-44635: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in kysely-org kysely
Description
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.
CVSS v3.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Kysely, a type-safe TypeScript SQL query builder, has a vulnerability (CVE-2026-44635) in versions 0.26.0 through 0.28.16 where DefaultQueryCompiler.visitJSONPathLeg does not properly escape JSON-path metacharacters such as ., [, ], *, **, and ?. When attacker-controlled input is passed to eb.ref(col, '->$').key(input) or .at(input), each dot character is interpreted as a path-leg separator. This allows traversal from the intended JSON key into sibling and child fields that developers did not intend to expose. This results in unauthorized read access and, in update statements, write access to JSON sub-fields across MySQL, PostgreSQL, and SQLite databases. The issue is resolved in version 0.28.17.
Potential Impact
The vulnerability allows an attacker to bypass intended JSON key restrictions and access or modify JSON sub-fields outside the authorized scope. This can lead to unauthorized data disclosure and unauthorized data modification in affected databases. The impact is limited to JSON data fields accessed via the vulnerable Kysely versions. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
A fix is available in Kysely version 0.28.17. Users should upgrade to version 0.28.17 or later to remediate this vulnerability. Since this is a library vulnerability, applying the official patch by upgrading is the recommended mitigation. Patch status is confirmed by the vendor advisory stating the issue is fixed in 0.28.17.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-07T15:30:10.875Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a173900e29bf47b50dc2e32
Added to database: 05/27/2026, 18:33:36 UTC
Last enriched: 06/03/2026, 20:52:08 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 94
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.