NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2023-22580 — sequelize

MEDIUMFix: sequelize/sequelize#15375

CVE-2023-22580 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in sequelize. A fix is available for sequelize — see the affected versions and patch details below.

Sequalize - Bad query filtering leading to SQL errors

Also known asGHSA-8c25-f3mj-v6h8
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-22580.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk
0.00%0.36%0.72%1.08%0.3%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

7Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
sequelizenpm
4.1Mdownloads / week
@sequelize/corenpm
79Kdownloads / week

Description

Due to improper input filtering in the sequalize js library, can malicious queries lead to sensitive information disclosure.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmsequelizeall versions6.28.1npm install sequelize@6.28.1
📦npm@sequelize/coreall versions7.0.0-alpha.20npm install @sequelize/core@7.0.0-alpha.20

Affected Products

1 product · 26 configurations
Application
sequelizesequelizejs
< 6.28.1
1 version
7.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sequelize, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update sequelize to 6.28.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-22580 is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

Due to improper input filtering in the sequalize js library, can malicious queries lead to sensitive information disclosure.
O3 Security · Impact-Aware SCA

Is CVE-2023-22580 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2023-22580: sequelize — Fixed in 6.28.1