fix(deps): update dependency drizzle-orm to v0.45.2 [security] - #144
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
2 times, most recently
from
April 27, 2026 21:18
2ea6ff2 to
ecc8f25
Compare
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
from
May 12, 2026 09:18
ecc8f25 to
2673061
Compare
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
from
July 12, 2026 10:50
2673061 to
67d6b02
Compare
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
from
July 16, 2026 18:12
67d6b02 to
457ea3d
Compare
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
from
July 21, 2026 02:28
457ea3d to
b0ef4ea
Compare
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
from
July 24, 2026 17:14
b0ef4ea to
2cd8e94
Compare
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
from
August 26, 2026 20:16
2cd8e94 to
85b164f
Compare
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
from
September 2, 2026 22:17
85b164f to
e5216e8
Compare
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
from
September 9, 2026 23:12
e5216e8 to
8855b90
Compare
renovate
Bot
force-pushed
the
renovate/npm-drizzle-orm-vulnerability
branch
from
September 10, 2026 22:47
8855b90 to
f318382
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.45.1→0.45.2Drizzle ORM has SQL injection via improperly escaped SQL identifiers
CVE-2026-39356 / GHSA-gpj5-g38j-94v9
More information
Details
Summary
Drizzle ORM improperly escaped quoted SQL identifiers in its dialect-specific
escapeName()implementations. In affected versions, embedded identifier delimiters were not escaped before the identifier was wrapped in quotes or backticks.As a result, applications that pass attacker-controlled input to APIs that construct SQL identifiers or aliases, such as
sql.identifier(),.as(), may allow an attacker to terminate the quoted identifier and inject SQL.Affected components
The issue affects the identifier escaping logic used by the PostgreSQL, MySQL, SQLite, SingleStore, and Gel dialects.
Impact
This issue only affects applications that pass untrusted runtime input into identifier or alias construction. Common examples include dynamic sorting, dynamic report builders, and CTE or alias names derived from request parameters.
Depending on the database dialect, query context, and database permissions, successful exploitation may enable blind or direct data disclosure, schema enumeration, query manipulation, privilege escalation, or destructive operations.
Applications that use only static schema objects, or that strictly map user input through an allowlist of known column or alias names, are not affected.
Details
In affected versions,
escapeName()wrapped the identifier but did not escape the quote delimiter inside the identifier value:"was not doubled to""`was not doubled to``Because of this, crafted input containing the dialect-specific identifier delimiter could break out of the quoted identifier and be interpreted as SQL syntax.
A representative vulnerable pattern is dynamic sorting using untrusted input: