CVE-2016-10543: Route Validation Bypass in call
Summary
CVE-2016-10543: Route Validation Bypass in call. Affects call versions >= 2.0.1, < 3.0.2. Fixed in 3.0.2. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The 'call' package is an npm package that provides functionality for making HTTP requests. It is commonly used in Node.js applications to handle API calls. The package allows developers to define routes and perform various operations on them. However, versions of 'call' prior to 3.0.2 are vulnerable to a route validation bypass.
Vulnerability Detail
The vulnerability in 'call' arises from the lack of validation for empty parameters. This allows an attacker to bypass route validation rules by sending a request with empty parameters. By exploiting this vulnerability, an attacker can potentially access sensitive information or perform unauthorized actions on the affected system.
How To Fix
Latest published version: 5.0.3 as of 22 Oct 2026
npm install call@5.0.3Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
3.0.2
This is the first release that contains the fix.
npm install call@3.0.2Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
The 'call' package prior to version 3.0.2 is vulnerable to a route validation bypass, which can be exploited to bypass route validation rules. To mitigate this vulnerability, it is crucial to update to version 3.0.2 or later. For additional support and guidance, you can reach out to DevNack.com.
See every vulnerability recorded for call →
FAQ
This vulnerability allows an attacker to bypass route validation rules, potentially leading to unauthorized access or actions on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including this one.
No, only versions prior to 3.0.2 are affected. It is recommended to update to version 3.0.2 or later to mitigate the vulnerability.
There is no known exploit available for this vulnerability at the moment. However, it is important to update to the latest version to prevent any potential exploitation.
For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in fixing this vulnerability.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
