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

GHSA-mqr2-w7wj-jjgr

MEDIUMFix: sidorares/node-mysql2#2424

GHSA-mqr2-w7wj-jjgr is a medium-severity (CVSS 6.5) Improper Input Validation vulnerability in mysql2. O3 Security confirms whether GHSA-mqr2-w7wj-jjgr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

mysql2 cache poisoning vulnerability

Also known asCVE-2024-21507
Published
Apr 10, 2024
Updated
Feb 4, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Feb 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

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

mysql2npm
14.3Mdownloads / week

Description

Versions of the package mysql2 before 3.9.3 are vulnerable to Improper Input Validation through the keyFromFields function, resulting in cache poisoning. An attacker can inject a colon : character within a value of the attacker-crafted key.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmysql2all versions3.9.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mysql2. 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 mysql2 to 3.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mqr2-w7wj-jjgr 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 GHSA-mqr2-w7wj-jjgr 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 GHSA-mqr2-w7wj-jjgr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of the package mysql2 before 3.9.3 are vulnerable to Improper Input Validation through the `keyFromFields` function, resulting in cache poisoning. An attacker can inject a colon `:` character within a value of the attacker-crafted key.
O3 Security · Impact-Aware SCA

Is GHSA-mqr2-w7wj-jjgr in your dependencies?

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

GHSA-mqr2-w7wj-jjgr: mysql2 cache… | O3 Security