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

CVE-2020-36650 — gry

HIGHFix: IonicaBizau/node-gry@5108446

CVE-2020-36650 is a high-severity (CVSS 8) CWE-77 vulnerability in gry. A fix is available for gry — see the affected versions and patch details below.

gry vulnerable to Command Injection

Also known asGHSA-w5mw-f2hq-5fw8
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.2%probability of exploitation in next 30 days
Lower Risk+0.10%
Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk
0.17%1.01%1.85%2.69%0.7%2.2%Apr 26Aug 26Oct 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

1 pkg 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.

18other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
grynpm
61Kdownloads / week

Description

A vulnerability, which was classified as critical, was found in IonicaBizau node-gry up to 5.x. This affects an unknown part. The manipulation leads to command injection. Upgrading to version 6.0.0 is able to address this issue. The name of the patch is 5108446c1e23960d65e8b973f1d9486f9f9dbd6c. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-218019.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmgryall versions6.0.0npm install gry@6.0.0

Affected Products

1 product · 1 configurations
Application
grygry_project
< 6.0.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update gry to 6.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-36650 is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

A vulnerability, which was classified as critical, was found in IonicaBizau node-gry up to 5.x. This affects an unknown part. The manipulation leads to command injection. Upgrading to version 6.0.0 is able to address this issue. The name of the patch is 5108446c1e23960d65e8b973f1d9486f9f9dbd6c. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-218019.
O3 Security · Impact-Aware SCA

Is CVE-2020-36650 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-36650: gry Command Injection — Fixed in 6.0.0