Vulnerability Database · npm · cd-messenger · Version
cd-messenger 2.0.0-build.161
2.0.0-build.161 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 29 Dec 2016
Licence MIT
Also known from other sources 1
Newer releases 62
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
cd-messenger 2.0.0-build.161 vulnerabilities
1 vulnerability cover cd-messenger 2.0.0-build.161. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Code Injection in cd-messenger | 9.8 critical | No fix published | 17 May 2021 |
Looking for another version, or everything Vulert holds for cd-messenger?
Questions
About cd-messenger 2.0.0-build.161
Is cd-messenger 2.0.0-build.161 vulnerable?
Yes. 1 vulnerability in the Vulert database cover cd-messenger 2.0.0-build.161: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 2.0.0-build.161 the latest release of cd-messenger?
No. 2.0.0-build.161 was published 29 Dec 2016, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor cd-messenger for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the cd-messenger version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.