CVE-2016-10626: mystem3 is a NodeJS wrapper for the Yandex MyStem 3
CVE-2016-10626 is a high-severity flaw (CVSS 8.1) affecting mystem3. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
mystem3 is a NodeJS wrapper for the Yandex MyStem 3. mystem3 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
A fixed release or distro patch exists.
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-10626?
mystem3: upgrade to newer than 1.0.7. Exact commands for each OS are on this page.
Is CVE-2016-10626 being exploited?
CVE-2016-10626 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-10626 affect?
CVE-2016-10626 affects mystem3. Severity is high (CVSS 8.1). mystem3 is a NodeJS wrapper for the Yandex MyStem 3. mystem3 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
How urgent is CVE-2016-10626?
Priority 52/100. High severity; Remotely exploitable, no login, no user action