CVE-2026-69240: Sequelize SQL Injection Vulnerability in Oracle DB

sequelize Updated 04 Aug 2026

Summary

03/08/2026
Yes i
Critical
9.8

CVE-2026-69240: Sequelize: SQL Injection (Oracle DB). Affects sequelize versions < 6.37.4. Fixed in 6.37.4. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Sequelize is a promise-based Node.js ORM (Object-Relational Mapping) that supports various SQL dialects, including PostgreSQL, MySQL, MariaDB, SQLite, and Oracle. It allows developers to interact with databases using JavaScript objects instead of SQL queries, simplifying database operations. However, a critical SQL injection vulnerability has been identified in the Oracle DB dialect, which can lead to unauthorized data access and manipulation.

Vulnerability Detail

The vulnerability arises from the escape function in sql-string.js, which fails to properly escape quotes in strings that start with TO_TIMESTAMP or TO_DATE when the dialect is set to 'oracle'. This oversight allows attackers to inject arbitrary SQL expressions into queries, potentially leading to data theft and tampering. For instance, an attacker can manipulate the firstName parameter in a query to execute malicious SQL code, compromising the integrity and confidentiality of the database.

How To Fix

Latest published version: 6.37.8 as of 23 Oct 2026

npm install sequelize@6.37.8

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

6.37.4

This is the first release that contains the fix.

npm install sequelize@6.37.4

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, avoid using user input directly in queries. Instead, use parameterized queries or prepared statements to ensure that user input is treated as data rather than executable code. For example, modify the code as follows:

var result = await models.Student.findOne({
  where: {
    firstName: {
      [Op.eq]: req.query.firstName
    }
  }
});

This approach helps prevent SQL injection by ensuring that user input is safely handled.

Conclusion

The SQL injection vulnerability in Sequelize when using Oracle DB is a critical issue that requires immediate attention. By updating to the patched version and implementing secure coding practices, developers can protect their applications from potential attacks. Utilizing tools like Vulert can further enhance security by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for sequelize →

Share this vulnerability

FAQ

The vulnerability has a CVSS score of 9.8, indicating a critical level of risk.

The vulnerability affects Sequelize versions prior to 6.37.4.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If exploited, this vulnerability can lead to unauthorized data access, data tampering, and potentially complete control over the database.

Yes, using parameterized queries or prepared statements can help mitigate the risk of SQL injection without requiring an immediate update.

Related vulnerabilities

Recent vulnerabilities recorded for sequelize.

How To Fix

Latest published version: 6.37.8 as of 23 Oct 2026

npm install sequelize@6.37.8

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

6.37.4

This is the first release that contains the fix.

npm install sequelize@6.37.4

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback