# CVE-2026-39356: SQL Injection via escapeName() in all Drizzle ORM SQL dialects

> Attackers can inject SQL via improper identifier escaping in Drizzle ORM, potentially leading to data theft or modification.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-gpj5-g38j-94v9

## What is CVE-2026-39356?

CVE-2026-39356 is a high-severity SQL injection vulnerability in drizzle-team drizzle-orm, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Drizzle is a modern TypeScript ORM. Prior to 0.45.2 and 1.0.0-beta.20, 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. This vulnerability is fixed in 0.45.2 and 1.0.0-beta.20.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-39356?

4 open source packages ship an affected version, including drizzle-orm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drizzle-orm` | npm | All versions | 0.45.2 |
| `drizzle-orm` | npm | All versions | 0.45.2 |
| `drizzle-orm` | npm | From 1.0.0-beta.2 | 1.0.0-beta.20 |
| `drizzle-orm` | npm | From 1.0.0-beta.2 | 1.0.0-beta.20 |

Products: Drizzle Drizzle.

## How do I fix CVE-2026-39356?

Upgrade drizzle-orm to a fixed version for your release line: 0.45.2 or 1.0.0-beta.20.

## Is CVE-2026-39356 being exploited?

There is no known exploitation of CVE-2026-39356 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-39356 and fix it if it is affected.

What it is: CVE-2026-39356 is a high-severity SQL injection vulnerability in drizzle-team drizzle-orm, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-39356 in the wild and no public exploit code.

Affected packages and fixed versions:
- drizzle-orm (npm): affected all versions; fixed in 0.45.2
- drizzle-orm (npm): affected all versions; fixed in 0.45.2
- drizzle-orm (npm): affected from 1.0.0-beta.2; fixed in 1.0.0-beta.20
- drizzle-orm (npm): affected from 1.0.0-beta.2; fixed in 1.0.0-beta.20

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-39356/ (Markdown: https://insights.sbomify.com/CVE-2026-39356/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-39356
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-39356
- OSV: https://osv.dev/vulnerability/CVE-2026-39356

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-39356/
Summaries are generated and may contain mistakes; the official description above is the record.