CVE-2026-69240
Received Received - Intake

SQL Injection in Sequelize via Oracle TO_TIMESTAMP

Publication date: 2026-08-03

Last updated on: 2026-08-03

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-03
Last Modified
2026-08-03
Generated
2026-08-04
AI Q&A
2026-08-04
EPSS Evaluated
N/A
NVD
CVE-2026-69240
EUVD
EUVD-2026-52429

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
sequelize sequelize 6.37.4

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a SQL injection vulnerability in Sequelize, a Node.js ORM tool. It affects versions before 6.37.4 when the Oracle dialect is used. The issue occurs because the escape function does not properly handle strings starting with TO_TIMESTAMP or TO_DATE, allowing attackers to inject arbitrary SQL expressions through application inputs.

Detection Guidance

Detection requires checking if your Sequelize version is below 6.37.4 and if the Oracle dialect is used. Inspect package.json for Sequelize version. No specific commands are provided in the context.

Impact Analysis

An attacker could exploit this to execute malicious SQL commands on your database, potentially leading to unauthorized data access, data manipulation, or complete system compromise. This could result in sensitive data breaches, data loss, or service disruption.

Compliance Impact

This vulnerability could lead to violations of GDPR (data protection) and HIPAA (health data privacy) by enabling unauthorized access to sensitive personal or health information. Organizations may face legal penalties, reputational damage, and loss of trust due to non-compliance.

Mitigation Strategies

Upgrade Sequelize to version 6.37.4 or later. If using the Oracle dialect, ensure input validation is in place to prevent SQL injection. Review applications for strings starting with TO_TIMESTAMP or TO_DATE.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-69240. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart