Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2023-22578

CRITICAL

CVE-2023-22578 is a critical-severity (CVSS 10) CWE-790 vulnerability in @sequelize/core. O3 Security confirms whether CVE-2023-22578 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Sequalize - Default support for “raw attributes” when using parentheses

Also known asGHSA-f598-mfpv-gmfx
Published
Feb 16, 2023
Updated
Jul 15, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Jul 15, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@sequelize/corenpm
40Kdownloads / week
sequelizenpm
2.9Mdownloads / week

Description

Due to improper artibute filtering in the sequalize js library, can a attacker peform SQL injections.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npm@sequelize/coreall versions7.0.0-alpha.20
📦npmsequelizeall versions6.29.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/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update @sequelize/core to 7.0.0-alpha.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-22578 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-22578 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-22578. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Due to improper artibute filtering in the sequalize js library, can a attacker peform SQL injections.
O3 Security · Impact-Aware SCA

Is CVE-2023-22578 in your dependencies?

O3 detects CVE-2023-22578 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.