CVE-2026-69240
CriticalCVSS 9.8Exploitation Probability (EPSS)
Low risk33th percentile - higher than 33% of all known CVEs
Summary
Sequelize, a Node.js ORM tool, is vulnerable to SQL injection in the Oracle dialect. The escape function fails to escape quotes when the value starts with TO_TIMESTAMP or TO_DATE, allowing arbitrary SQL injection.
Risk Assessment
An attacker can execute unauthorized SQL queries on the Oracle database, potentially leading to data leakage or modification.
Recommendation
Upgrade Sequelize to version 6.37.4 or later.
Other vulnerabilities in Sequelize
See all- CVE-2015-1369High
SQL injection vulnerability in Sequelize before version 2.0.0-rc7 for Node.js allows remote attackers to execute arbitrary SQL commands via the order parameter.
- CVE-2026-30951High
Sequelize before version 6.37.8 contains an SQL injection vulnerability via unescaped cast type in JSON/JSONB WHERE clause processing. The _traverseJSON() function splits JSON path keys on '::' to extract a cast type, which is interpolated raw into CAST(... AS <type>) SQL. An attacker who controls JSON object keys can inject arbitrary SQL and exfiltrate data from any table.
Original NVD description (English source)
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.

