Security readout for executives and security teams
Plain-English summary
A flaw in Sequelize can let remote attackers turn attacker-controlled JSON keys into SQL. In exposed applications, this may allow confidential data to be read from database tables. The issue affects Sequelize from 6.0.0-beta.1 through 6.37.7 and is fixed in 6.37.8.
Executive priority
Prioritize prompt remediation for affected public applications because exploitation may require no authentication and could expose sensitive database information. Accelerate systems accepting flexible JSON filters or object-shaped query input. Current sources do not establish active exploitation, so emergency incident status should depend on confirmed exposure or suspicious evidence.
Technical view
Sequelize’s _traverseJSON() interprets text after :: in JSON path keys as a cast type, then inserts that type unescaped into CAST(... AS <type>) SQL. Applications are vulnerable when attacker-controlled object keys reach JSON or JSONB where-clause processing. This is CWE-89 with CVSS 3.1 score 7.5.
Likely exposure
Exposure is most likely in Node.js applications using affected Sequelize versions that allow untrusted JSON object keys to influence JSON or JSONB query filters. Merely installing Sequelize does not establish exploitability; the vulnerable data flow must be reachable. Internet-facing, unauthenticated query endpoints warrant the fastest review.
Exploitation context
The CVSS vector describes network access, low complexity, no required privileges, and no user interaction, with high confidentiality impact. The supplied record is not listed in KEV and provides no evidence of active exploitation. Treat exploitation status as unconfirmed, not absent.
Researcher notes
The vulnerable primitive is raw cast-type interpolation during JSON path traversal, not general use of JSON columns. Validate reachability at the application boundary and ORM query-building layer. The supplied sources state arbitrary SQL and cross-table data exfiltration are possible, but provide no confirmed exploitation telemetry.
Mitigation direction
- Upgrade Sequelize to version 6.37.8 or later.
- Identify and prioritize internet-facing applications using affected Sequelize versions.
- Prevent untrusted JSON keys from reaching Sequelize JSON or JSONB where clauses until upgraded.
- Review applicable vendor guidance and Red Hat errata for packaged deployments.
Validation and detection
- Check manifests, lockfiles, and deployed runtime dependencies for Sequelize versions before 6.37.8.
- Trace whether user-controlled JSON object keys reach Sequelize where-clause construction.
- Confirm production resolves and loads Sequelize 6.37.8 or later after deployment.
- Test affected request paths to ensure untrusted cast-like JSON keys are rejected safely.
- Review application logs for unexpected JSON keys containing cast delimiters.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-30951 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-03-10T21:01:17.729Z: Reported to Red Hat.
- 2026-03-10T20:22:46.150Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/sequelize/sequelize/security/advisories/GHSA-6457-6jrx-69crCVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-30951CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2446250CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-30951.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:8498CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.