CVE-2016-10626: Insecure Download of Executable in mystem3

mystem3 Updated 02 Oct 2025

Summary

18/02/2019
Yes i
High
8.1

CVE-2016-10626: Downloads Resources over HTTP in mystem3. Affects mystem3 versions < 1.0.8. Fixed in 1.0.8. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

mystem3 is an npm package that provides a tool for morphological analysis of Russian texts. It is commonly used in natural language processing applications. The package allows users to analyze and process Russian text by providing linguistic information such as word forms, lemmas, and grammatical tags. However, versions of mystem3 prior to 1.0.8 are vulnerable to an insecure download of an executable over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in mystem3 arises from the insecure download of an executable file over an unencrypted HTTP connection. This means that if an attacker has a privileged network position, they can intercept the response and replace the downloaded executable with a malicious one. When the system running mystem3 executes the downloaded file, it can lead to arbitrary code execution. This vulnerability poses a significant risk as it allows an attacker to compromise the integrity and security of the system.

How To Fix

Minimum fixed version

1.0.8

This is the first release that contains the fix.

npm install mystem3@1.0.8

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. It is crucial to update to the latest version of mystem3 to address the issue.

Conclusion

The vulnerability in mystem3 allows an attacker to replace the downloaded executable with a malicious one, leading to arbitrary code execution. To mitigate this risk, it is crucial to update mystem3 to version 1.0.8 or later. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for mystem3 →

Share this vulnerability

FAQ

mystem3 is an npm package used for morphological analysis of Russian texts. It provides linguistic information about word forms, lemmas, and grammatical tags.

The vulnerability allows an attacker to replace the downloaded executable with a malicious one, leading to arbitrary code execution on the system running mystem3.

To fix the vulnerability, update mystem3 to version 1.0.8 or later.

No, there is no specific workaround. Updating to the latest version is the recommended solution.

You can find more information about this vulnerability in the GitHub Advisory Database.

How To Fix

Minimum fixed version

1.0.8

This is the first release that contains the fix.

npm install mystem3@1.0.8

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback