CVE-2026-69240 Sequelize: SQL Injection (Oracle DB)
Attackers can inject arbitrary SQL via specific string inputs when using the Oracle dialect, requiring an upgrade to the Sequelize library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-69240?
CVE-2026-69240 is a critical SQL injection vulnerability in sequelize, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Sequelize is a Node.js ORM tool. Prior to 6.37.4, SQL injection is possible with strings only if dialect is set to oracle. The escape function defined in sql-string.js does not escape quotes if the value starts with TO_TIMESTAMP or TO_DATE. In the Oracle dialect, when val is a string and starts with TO_TIMESTAMP or TO_DATE, escape returns val directly instead of replacing single quotes. An attacker can inject arbitrary SQL expressions through an application value that reaches this escape path. This issue is fixed in version 6.37.4.
Weakness: CWE-89
Which versions are affected by CVE-2026-69240?
2 open source packages ship an affected version, including sequelize.
| Package | Affected | Fixed in |
|---|---|---|
sequelize npm | All versions | 6.37.4 |
sequelize npm | All versions | 6.37.4 |
How do I fix CVE-2026-69240?
Upgrade sequelize to 6.37.4 or later.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-69240 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69240 exists.
Sources
Also known as GHSA-v8fg-2rw7-q452.