CVE-2016-10580: Insecure Download of Resources in nodewebkit

nodewebkit Updated 02 Oct 2025

Summary

18/02/2019

Disclosed on

CVE-2016-10580

CVE

No i

Fix available

High

Severity

Not published

CVSS Score

CVE-2016-10580: Downloads Resources over HTTP in nodewebkit. Affects nodewebkit versions < 0.11.6. No fix is published. 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 Browse

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.

Background

nodewebkit is an npm package that allows developers to build desktop applications using web technologies. It provides a framework for creating cross-platform applications using HTML, CSS, and JavaScript. The package has been deprecated by the author, and the official recommendation is to use the official installer instead. However, affected versions of nodewebkit insecurely download an executable over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in nodewebkit arises from the insecure downloading of an executable over an unencrypted HTTP connection. This means that if an attacker has a privileged network position, they can intercept the response and replace the executable with a malicious one. This could lead to code execution on the system running nodewebkit. The impact of this vulnerability is significant as it allows an attacker to compromise the integrity and security of the system.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As mentioned earlier, the recommended workaround is to use the official installer instead of nodewebkit. This ensures that the executable is downloaded securely over HTTPS, reducing the risk of interception and replacement by an attacker.

Conclusion

In conclusion, nodewebkit is vulnerable to an insecure download of resources over an unencrypted HTTP connection. This vulnerability can be mitigated by using the official installer from the npm website. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for nodewebkit →