PatchTheCVECVE-2016-10614: httpsync is a port of libcurl to node.js
CVE-2016-10614 is a high-severity flaw (CVSS 8.1) affecting httpsync. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
httpsync is a port of libcurl to node.js. httpsync downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2016-10614?
httpsync: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2016-10614 being exploited?
CVE-2016-10614 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2016-10614 affect?
CVE-2016-10614 affects httpsync. Severity is high (CVSS 8.1). httpsync is a port of libcurl to node.js. httpsync downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attack
How urgent is CVE-2016-10614?
Priority 53/100. High severity; Remotely exploitable, no login, no user action
Software pages
Node.js vulnerabilities · curl vulnerabilities