SQL Injection in Sequelize is a Node.js ORM tool. Prior to (CVE-2026-30951)
Summary
SQL injection in Sequelize is a Node.js ORM tool. Prior to (CVE-2026-30951). Confidential information can be exposed externally. Mitigation: upgrade to 6.37.8 or later.
Original description
The description as published by the source.
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 ) 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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-30951 has been found in Sequelize is a Node.js ORM tool. Prior to.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade Sequelize is a Node.js ORM tool. Prior to to 6.37.8 or later.
If unsure, ask your IT team or search "Sequelize is a Node.js ORM tool. Prior to CVE-2026-30951" on the vendor's site.
CVE-2026-30951 (Sequelize is a Node.js ORM tool. Prior to) — CWE-89 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 6.37.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in Sequelize is a Node.js ORM tool. Prior to.
Check the vendor advisory for the affected versions of Sequelize is a Node.js ORM tool. Prior to.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 6.37.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Sequelize is a Node.js ORM tool. Prior to を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Sequelize is a Node.js ORM tool. Prior to to 6.37.8ステージング環境で 6.37.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory github.com
- advisory nvd.nist.gov
- report bugzilla.redhat.com
- web security.access.redhat.com