Skip to content

chore(deps): update dependency drizzle-orm to v0.45.2 [security]#276

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-drizzle-orm-vulnerability
Open

chore(deps): update dependency drizzle-orm to v0.45.2 [security]#276
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-drizzle-orm-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 8, 2026

This PR contains the following updates:

Package Change Age Confidence
drizzle-orm (source) 0.44.60.45.2 age confidence

GitHub Vulnerability Alerts

CVE-2026-39356

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:

  • PostgreSQL / SQLite / Gel: " was not doubled to ""
  • MySQL / SingleStore: ` 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:

const sortField = req.query.sort || 'id';

const rows = await db
  .select()
  .from(users)
  .orderBy(sql.identifier(sortField));

---

### Release Notes

<details>
<summary>drizzle-team/drizzle-orm (drizzle-orm)</summary>

### [`v0.45.2`](https://redirect.github.com/drizzle-team/drizzle-orm/releases/tag/0.45.2)

[Compare Source](https://redirect.github.com/drizzle-team/drizzle-orm/compare/0.45.1...0.45.2)

- Fixed `sql.identifier()`, `sql.as()` escaping issues. Previously all the values passed to this functions were not properly escaped
  causing a possible SQL Injection (CWE-89) vulnerability

Thanks to [@&#8203;EthanKim88](https://redirect.github.com/EthanKim88), [@&#8203;0x90sh](https://redirect.github.com/0x90sh) and [@&#8203;wgoodall01](https://redirect.github.com/wgoodall01) for reaching out to us with a reproduction and suggested fix

### [`v0.45.1`](https://redirect.github.com/drizzle-team/drizzle-orm/releases/tag/0.45.1)

[Compare Source](https://redirect.github.com/drizzle-team/drizzle-orm/compare/0.45.0...0.45.1)

- Fixed pg-native Pool detection in node-postgres transactions breaking in environments with forbidden `require()` ([#&#8203;5107](https://redirect.github.com/drizzle-team/drizzle-orm/issues/5107))

### [`v0.45.0`](https://redirect.github.com/drizzle-team/drizzle-orm/releases/tag/0.45.0)

[Compare Source](https://redirect.github.com/drizzle-team/drizzle-orm/compare/0.44.7...0.45.0)

- Fixed pg-native Pool detection in node-postgres transactions
- Allowed subqueries in select fields
- Updated typo algorythm => algorithm
- Fixed `$onUpdate` not handling `SQL` values (fixes [#&#8203;2388](https://redirect.github.com/drizzle-team/drizzle-orm/issues/2388), tests implemented by [L-Mario564](https://redirect.github.com/L-Mario564) in [#&#8203;2911](https://redirect.github.com/drizzle-team/drizzle-orm/pull/2911))
- Fixed `pg` mappers not handling `Date` instances in `bun-sql:postgresql` driver responses for `date`, `timestamp` types (fixes [#&#8203;4493](https://redirect.github.com/drizzle-team/drizzle-orm/issues/4493))

### [`v0.44.7`](https://redirect.github.com/drizzle-team/drizzle-orm/releases/tag/0.44.7)

[Compare Source](https://redirect.github.com/drizzle-team/drizzle-orm/compare/0.44.6...0.44.7)

- fix durable sqlite transaction return value [#&#8203;3746](https://redirect.github.com/drizzle-team/drizzle-orm/issues/3746) - thanks [@&#8203;joaocstro](https://redirect.github.com/joaocstro)

</details>

---

### Configuration

📅 **Schedule**: (UTC)

- Branch creation
  - ""
- Automerge
  - "after 1am and before 2am"

🚦 **Automerge**: Enabled.

 **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/nextorders/roll-stack).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMDIuMTEiLCJ1cGRhdGVkSW5WZXIiOiI0My4xMTAuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->

@renovate renovate bot added the dependencies label Apr 8, 2026
@renovate renovate bot requested a review from hmbanan666 as a code owner April 8, 2026 05:28
@socket-security
Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updateddrizzle-orm@​0.44.6 ⏵ 0.45.298 +1100 +1688 +199100

View full report

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 3 files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants