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

GHSA-m8xj-5v73-3hh8

CRITICAL

GHSA-m8xj-5v73-3hh8 is a critical-severity (CVSS 9.8) OS Command Injection vulnerability in curlrequest. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-m8xj-5v73-3hh8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

curlrequest allows execution of arbitrary commands

Also known asCVE-2020-7646SNYK-JS-CURLREQUEST-568274
Published
May 13, 2020
Updated
Jul 8, 2026
Affected
1 pkg
Patched
None yet
Exploits
1 known
Exploitation data as of Jul 8, 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, and reverse-dependency count shows how many other packages break if it stays unpatched.

47other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
curlrequestnpm
1Kdownloads / week

Description

curlrequest through 1.0.1 allows execution of arbitrary commands. It is possible to inject arbitrary commands by using a semicolon char in any of the options values.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmcurlrequestall versionsNo fix
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for curlrequest. 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. Remediation status

    No patched version of curlrequest has shipped for GHSA-m8xj-5v73-3hh8 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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-m8xj-5v73-3hh8 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-m8xj-5v73-3hh8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

curlrequest through 1.0.1 allows execution of arbitrary commands. It is possible to inject arbitrary commands by using a semicolon char in any of the `options` values.
O3 Security · Impact-Aware SCA

Is GHSA-m8xj-5v73-3hh8 in your dependencies?

O3 detects GHSA-m8xj-5v73-3hh8 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-m8xj-5v73-3hh8: curlrequest allows… | O3 Security