# Sequelize SQLite dialect denial of service

Source: https://junglewise.ai/threats/sequelize-sqlite-dialect-denial-of-service-25dad2fa  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2020-09-03. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

Severity: info · Published 2020-09-03

Sequelize is a popular Node.js ORM (Object-Relational Mapping) library used to interact with databases. Versions before 4.44.4 contain a defect in the SQLite dialect that crashes the Node.js process when certain database operations are performed, allowing attackers to cause application downtime by submitting specially crafted input.

Technologies: [sequelize (npm)](https://junglewise.ai/threats/technologies/sequelize). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** Informational severity, published 3 September 2020.

**Which products and versions are affected?** sequelize (npm) SEMVER:introduced=0,fixed=4.44.4.

**Is there a fix for This vulnerability?** Yes. sequelize (npm): upgrade to 4.44.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is This vulnerability attacked?** It is attacked over the network, in a software library.

**Am I affected?** 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 4.44.4 or later

  ```sh
  npm install sequelize@4.44.4
  ```


## Technical details

The vulnerability is a Denial of Service caused by an unhandled TypeError exception in the SQLite dialect of Sequelize prior to version 4.44.4. The root cause is a missing error handler around a `.map()` call on the `results` variable, which may be undefined in certain conditions. An attacker can trigger this by submitting malicious input that causes the results variable to be undefined, leading to an uncaught exception that crashes the entire Node.js process. This is a network-reachable vulnerability if the application exposes database operations to untrusted input. The fix is available in version 4.44.4 and later.

## Affected products

- Sequelize Sequelize < 4.44.4

## Timeline

- 2020-09-03: disclosed
- 2020-02-21: patched: Fix merged in PR #11877

## References

- [https://github.com/sequelize/sequelize/pull/11877](https://github.com/sequelize/sequelize/pull/11877)
- [https://www.npmjs.com/advisories/1142](https://www.npmjs.com/advisories/1142)

## Related threats

- [Sequelize SQL injection in Oracle dialect escape function](https://junglewise.ai/threats/cve-2026-69240-sequelize-sql-injection-in-oracle-dialect-escape-function)
- [Sequelize SQL injection in JSON where clause processing](https://junglewise.ai/threats/cve-2026-30951-sequelize-sql-injection-in-json-where-clause-processing)
- [Sequelize SQL injection via unescaped parentheses in attributes](https://junglewise.ai/threats/cve-2023-22578-sequelize-sql-injection-via-unescaped-parentheses-in-attributes)
- [Sequelize unsafe fall-through in getWhereConditions](https://junglewise.ai/threats/cve-2023-22579-sequelize-unsafe-fall-through-in-getwhereconditions)
- [Sequelize SQL injection via replacements](https://junglewise.ai/threats/cve-2023-25813-sequelize-sql-injection-via-replacements)