Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.8

Sequelize can be exploited for SQL injection with Oracle

CVE-2026-69240 · published 3 months ago
Summary

Versions of Sequelize before 6.37.4 do not properly escape certain Oracle date functions, allowing an attacker to insert malicious SQL when the application passes strings that start with TO_TIMESTAMP or TO_DATE. This risk only affects the Oracle database mode. Update Sequelize to version 6.37.4 or later to fix the problem.

What to do
  • Update wikirik sequelize to version 6.37.4.
Affected software
Ecosystem VendorProductAffected versions
– sequelize sequelize < 6.37.4
npm wikirik sequelize < 6.37.4
Fix: upgrade to 6.37.4
Original advisory text
Sequelize: SQL Injection (Oracle DB)
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.
References
Fix within
Internet-facing 3 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically
  • Gives an attacker full control
Severity
9.8 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-89SQL Injection
Timeline
Published3 Aug 2026
Updated4 Nov 2026
First seen3 Aug 2026
Sources
CVE-2026-69240 · NVD
CVE-2026-69240 · MITRE
GHSA-v8fg-2rw7-q452 · GHSA
CVE-2026-69240 · OSV
Track software like this
Free during beta