dbcve.org
DrizzleApplication

CVE-2026-39356

HIGH · 7.5 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 0.45.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Drizzle ORM versions prior to 0.45.2 and 1.0.0-beta.20 contain an SQL injection vulnerability in the dialect-specific escapeName() functions. These functions fail to escape embedded quote or backtick characters within SQL identifiers before wrapping them, allowing attackers to break out of quoted identifiers when passing attacker-controlled input to sql.identifier() or .as() APIs.

MitigationUpgrade Drizzle ORM to version 0.45.2, 1.0.0-beta.20, or later to obtain the patched escapeName() implementations that properly escape embedded delimiters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DrizzleApplication
Affected:< 0.45.2= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Drizzle ORM version
    Run 'npm list drizzle' or check the 'dependencies' or 'devDependencies' section in your project's package.json file to find the exact version of the drizzle package installed.
    Affected if The installed version is either 1.0.0 (exact match) or less than 0.45.2 (e.g., 0.45.1, 0.44.0, etc.).
  2. Locate usage of sql.identifier() method
    Search your codebase for occurrences of 'sql.identifier(' (or the equivalent from your Drizzle setup) to find where identifiers are being constructed programmatically.
    Affected if The codebase contains calls to sql.identifier() that accept dynamic or user-supplied values without prior sanitization.
  3. Locate usage of .as() alias method
    Search your codebase for '.as(' method calls on column or table references, which are also affected by this vulnerability.
    Affected if The codebase contains .as() method calls that accept user-supplied values as the alias name.
  4. Inspect identifier construction for quote characters
    Review the identified sql.identifier() and .as() call sites to determine whether the values passed to them could contain double quotes ("), backticks (`), or other quote characters.
    Affected if Any identified identifier construction passes values that could include unescaped quote characters from untrusted sources.

You are affected if your installed Drizzle ORM version is less than 0.45.2 or exactly 1.0.0 AND your code passes untrusted user input directly to sql.identifier() or .as() methods without sanitizing embedded quote characters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.45.2 or later
Fixed in 0.45.2
Interim mitigation

Upgrade Drizzle ORM to version 0.45.2, 1.0.0-beta.20, or later to obtain the patched escapeName() implementations that properly escape embedded delimiters.

Recommended fix High confidence

0.45.2 or 1.0.0-beta.20

  1. Run `npm install [email protected]` or `npm install [email protected]` to upgrade to a fixed version
  2. Verify the upgrade was successful by checking the installed version with `npm list drizzle-orm`
  3. Test that your application functionality remains intact after the upgrade
  4. If using yarn, run `yarn add [email protected]` or `yarn add [email protected]`
  5. If using pnpm, run `pnpm add [email protected]` or `pnpm add [email protected]`
Caveat beta version 1.0.0-beta.20 may contain other changes; review changelog before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Drizzle Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39356 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39356 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data