CVE-2026-69240: Sequelize: SQL Injection (Oracle DB)

Published Aug 3, 2026
·
Updated

Summary SQL Injection is possible with strings only if dialect is set to oracle. The vulnerability was confirmed on Sequelize v6.37.3.

Details The escape function defined in sql-string.js does not escape quotes if the value starts with TOTIMESTAMP or TODATE.

javascript } else if (dialect === 'oracle' && typeof val === 'string') { if (val.startsWith('TOTIMESTAMP') || val.startsWith('TODATE')) { return val; } val = val.replace(/'/g, "''"); }

PoC Suppose the application has the following code:

javascript var result = await models.Student.findOne({ where: { firstName: req.query.firstName } });

An attacker can inject arbitrary sql expressions.

http://host/path?firstName=TODATE('0','Y')||'' OR 1=1--

The resulted SQL will be:

SQL SELECT ... WHERE "Student"."firstName" = TODATE('0','Y')||'' OR 1=1-- ORDER BY "Student"."id" OFFSET 0 ROWS FETCH NEXT 1 ROWS ONLY;

Impact Data theft and tampering.

Other sources

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 TOTIMESTAMP or TODATE. In the Oracle dialect, when val is a string and starts with TOTIMESTAMP or TODATE, 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.

MITRE

Affected Software

2 affected componentsFixes available
npm/sequelize<6.37.4
npm/sequelize<6.37.4
6.37.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/sequelize to a version that resolves this vulnerability.

    Fixed in 6.37.4
  2. Upgrade

    Upgrade Sequelize to a version that resolves this vulnerability.

    Fixed in 6.37.4

Event History

Aug 3, 2026
CVE Published
via MITRE·08:28 PM
Data Sourced
via MITRE·08:28 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·08:29 PM
Data Sourced
via GitHub·08:29 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-69240?

CVE-2026-69240 has a critical severity rating of 9.8.

2

How do I fix CVE-2026-69240?

To fix CVE-2026-69240, upgrade Sequelize to version 6.37.4 or later.

3

What type of vulnerability is CVE-2026-69240?

CVE-2026-69240 is a SQL Injection vulnerability specifically affecting Oracle DB when using Sequelize.

4

Which versions of Sequelize are affected by CVE-2026-69240?

CVE-2026-69240 affects Sequelize version 6.37.3 and earlier.

5

How can CVE-2026-69240 be exploited?

CVE-2026-69240 can be exploited through unescaped strings leading to SQL Injection when the dialect is set to 'oracle'.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203