Quick answers
- Is CVE-2026-69240 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69240 being exploited in the wild.
- How severe is CVE-2026-69240?
- Critical severity, with a CVSS score of 9.8, published 3 August 2026.
- Which products and versions are affected?
- sequelize (npm) < 6.37.4, SEMVER:introduced=0,fixed=6.37.4.
- Is there a fix for CVE-2026-69240?
- Yes. sequelize (npm): upgrade to 6.37.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-69240 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-69240?
- Check whether you run sequelize (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- sequelize (npm): upgrade to 6.37.4 or later
npm install sequelize@6.37.4
Technical details
A SQL injection vulnerability exists in Sequelize's Oracle dialect implementation within `sql-string.js`. The `escape` function fails to sanitize single quotes if a string value begins with `TO_TIMESTAMP` or `TO_DATE`, returning the raw string instead of an escaped version. An attacker can exploit this by providing a crafted input that starts with one of these functions followed by malicious SQL syntax (e.g., using the `||` operator). This allows for arbitrary SQL expression injection without authentication. The issue is confirmed in version 6.37.3 and addressed in version 6.37.4.
Affected products
- Sequelize sequelize < 6.37.4
Identifiers
- CVE-2026-69240
- GHSA-v8fg-2rw7-q452
Timeline
- 2026-07-29: patched: Fix released in version 6.37.4
- 2026-08-03: advisory: GitHub Advisory published