Is this vulnerability remotely exploitable?

It can be remotely exploitable if external inputs (such as HTTP request parameters, headers, query strings, or multi-tenant identifiers) are passed into Drizzle APIs that build SQL identifiers or aliases without strict validation or allowlisting.

Does an attacker need authenticated access to exploit this?

That depends on where the identifier values come from. If only authenticated users can influence these values (e.g., tenant IDs in a logged-in context), then at least some form of authenticated access is required. If the values can be controlled by unauthenticated users (e.g., open APIs or public endpoints), exploitation may be possible without authentication.

What is the safest general fix pattern?

The safest pattern is to avoid constructing identifiers directly from user input. Instead, define a fixed mapping from external values to allowed identifiers, validate inputs against this mapping, and rely on the ORM's corrected escaping logic for the remaining dynamic parts. Treat identifier names like configuration, not free-form user data.

Severity:

HIGH RISK

(7.5)

SQL Injection via Improper Identifier Escaping (CWE-89) in Drizzle ORM

CVE-2026-39356

Published:

Apr 7, 2026

Status:

Undergoing Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI Handler setAccessDeviceCfg

Remote Code Execution on the Router

April 12, 2026

CWE-77;CWE-78

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI setLedCfg Handler

Remote Code Execution on the Router

April 12, 2026

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL Injection and Data Compromise

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Arbitrary SQL Injection and Data Compromise

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

SQL Injection via Improper Identifier Escaping (CWE-89) in Drizzle ORM

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI Handler setAccessDeviceCfg

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI setLedCfg Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare