# CVE-2026-30951: Sequelize v6 Vulnerable to SQL Injection via JSON Column Cast Type

> Attackers can inject arbitrary SQL via JSON column cast types in Sequelize, allowing data exfiltration from any table.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2026
- **Updated:** 20 Aug 2026
- **Also known as:** CLEANSTART-2026-AK68304, CLEANSTART-2026-YB83970, CLSA-2026-1792476615, GHSA-6457-6jrx-69cr

## What is CVE-2026-30951?

CVE-2026-30951 is a high-severity SQL injection vulnerability in sequelize, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sequelize is a Node.js ORM tool. Prior to 6.37.8, there is SQL injection via unescaped cast type in JSON/JSONB where clause processing. The _traverseJSON() function splits JSON path keys on :: to extract a cast type, which is interpolated raw into CAST(... AS <type>) SQL. An attacker who controls JSON object keys can inject arbitrary SQL and exfiltrate data from any table. This vulnerability is fixed in 6.37.8.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-30951?

2 open source packages ship an affected version, including sequelize. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sequelize` | npm | From 6.0.0-beta.1 | 6.37.8 |
| `sequelize` | npm | From 6.0.0-beta.1 | 6.37.8 |

Products: Sequelizejs Sequelize.

## How do I fix CVE-2026-30951?

Upgrade sequelize to 6.37.8 or later.

## Is CVE-2026-30951 being exploited?

There is no known exploitation of CVE-2026-30951 in the wild and no public exploit code.

Public exploit code:

- Sequelize JSON Cast SQL Injection (github_poc): https://github.com/EQSTLab/CVE-2026-30951
- https://github.com/yym8538/CVE-2026-30951 (github_poc): https://github.com/yym8538/CVE-2026-30951

## Other vulnerabilities in sequelize

- [CVE-2023-25813](https://insights.sbomify.com/CVE-2023-25813/): SQL Injection via replacements in sequelize (critical 10.0)
- [CVE-2023-22578](https://insights.sbomify.com/CVE-2023-22578/): Sequalize - Default support for “raw attributes” when using parentheses (critical 10.0)
- [CVE-2023-22579](https://insights.sbomify.com/CVE-2023-22579/): Sequalize - Unsafe fall-through in getWhereConditions (critical 9.9)
- [CVE-2019-10749](https://insights.sbomify.com/CVE-2019-10749/): SQL Injection in sequelize (critical 9.8)
- [CVE-2019-10748](https://insights.sbomify.com/CVE-2019-10748/): SQL Injection in sequelize (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30951 and fix it if it is affected.

What it is: CVE-2026-30951 is a high-severity SQL injection vulnerability in sequelize, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30951 in the wild and no public exploit code.

Affected packages and fixed versions:
- sequelize (npm): affected from 6.0.0-beta.1; fixed in 6.37.8
- sequelize (npm): affected from 6.0.0-beta.1; fixed in 6.37.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30951/ (Markdown: https://insights.sbomify.com/CVE-2026-30951/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30951
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30951
- OSV: https://osv.dev/vulnerability/CVE-2026-30951

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30951/
Summaries are generated and may contain mistakes; the official description above is the record.