VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

cd-messenger: vulnerability history, versions and safety

cd-messenger is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 62 releases, first recorded in May 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cd-messenger vulnerabilities

Vulert verdict on cd-messenger 2.7.26 i

Updated on 22 Oct 2026

Careful: 2.7.26 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 44/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.7.26 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 17 May 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Depended on by 1 packages i
  • Stars 1 i
  • OpenSSF scorecard 2/10 i
  • Last release 99 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for cd-messenger, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.7.26 03 Jul 2018 C1 MIT No Details →
2.7.24 11 Mar 2017 C1 MIT No Details →
2.7.23 11 Mar 2017 C1 MIT No Details →
2.7.22 11 Mar 2017 C1 MIT No Details →
2.7.21 11 Mar 2017 C1 MIT No Details →
2.7.20 11 Mar 2017 C1 MIT No Details →
2.7.19 11 Mar 2017 C1 MIT No Details →
2.7.17 11 Mar 2017 C1 MIT No Details →
2.7.16 01 Feb 2017 C1 MIT No Details →
2.7.14 01 Feb 2017 C1 MIT No Details →
2.7.12 29 Jan 2017 C1 MIT No Details →
2.7.11 27 Jan 2017 C1 MIT No Details →
2.7.10 27 Jan 2017 C1 MIT No Details →
2.7.9 27 Jan 2017 C1 MIT No Details →
2.7.8 25 Jan 2017 C1 MIT No Details →
2.7.7 21 Jan 2017 C1 MIT No Details →
2.7.6 21 Jan 2017 C1 MIT No Details →
2.7.5 21 Jan 2017 C1 MIT No Details →
2.7.4 21 Jan 2017 C1 MIT No Details →
2.7.3 21 Jan 2017 C1 MIT No Details →
2.7.2 21 Jan 2017 C1 MIT No Details →
2.7.1 21 Jan 2017 C1 MIT No Details →
2.7.0 21 Jan 2017 C1 MIT No Details →
2.6.1 21 Jan 2017 C1 MIT No Details →
2.6.0 21 Jan 2017 C1 MIT No Details →
2.5.2 21 Jan 2017 C1 MIT No Details →
2.5.1 20 Jan 2017 C1 MIT No Details →
2.5.0 20 Jan 2017 C1 MIT No Details →
2.4.1 20 Jan 2017 C1 MIT No Details →
2.3.5 20 Jan 2017 C1 MIT No Details →
2.3.3 19 Jan 2017 C1 MIT No Details →
2.3.2 19 Jan 2017 C1 MIT No Details →
2.3.1 19 Jan 2017 C1 MIT No Details →
2.3.0 18 Jan 2017 C1 MIT No Details →
2.2.3 18 Jan 2017 C1 MIT No Details →
2.2.2 18 Jan 2017 C1 MIT No Details →
2.2.1 18 Jan 2017 C1 MIT No Details →
2.2.1-build.24 18 Jan 2017 C1 MIT No Details →
2.2.1-build.7 18 Jan 2017 C1 MIT No Details →
2.2.0 18 Jan 2017 C1 MIT No Details →
2.1.1 17 Jan 2017 C1 MIT No Details →
2.1.0 17 Jan 2017 C1 MIT No Details →
2.0.6 17 Jan 2017 C1 MIT No Details →
2.0.5 15 Jan 2017 C1 MIT No Details →
2.0.3 04 Jan 2017 C1 MIT No Details →
2.0.1 04 Jan 2017 C1 MIT No Details →
2.0.0-build.219 04 Jan 2017 C1 MIT No Details →
2.0.0-build.217 04 Jan 2017 C1 MIT No Details →
2.0.0-build.210 03 Jan 2017 C1 MIT No Details →
2.0.0-build.209 03 Jan 2017 C1 MIT No Details →
2.0.0-build.208 03 Jan 2017 C1 MIT No Details →
2.0.0-build.207 03 Jan 2017 C1 MIT No Details →
2.0.0-build.204 03 Jan 2017 C1 MIT No Details →
2.0.0-build.203 03 Jan 2017 C1 MIT No Details →
2.0.0-build.187 03 Jan 2017 C1 MIT No Details →
2.0.0-build.181 01 Jan 2017 C1 MIT No Details →
2.0.0-build.180 31 Dec 2016 C1 MIT No Details →
2.0.0-build.163 29 Dec 2016 C1 MIT No Details →
2.0.0-build.161 29 Dec 2016 C1 MIT No Details →
2.0.0-build.160 29 Dec 2016 C1 MIT No Details →
2.0.0-build.155 29 Dec 2016 C1 MIT No Details →
2.0.0 11 Aug 2016 C1 MIT No Details →

All 62 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for cd-messenger

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Code Injection in cd-messenger 9.8 critical No fix published 17 May 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 →

Questions

About cd-messenger

Is cd-messenger safe to use?

Vulert records 1 vulnerabilities for cd-messenger in npm: 1 critical, 0 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is cd-messenger's Vulert package health score?

Vulert scores cd-messenger 44/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of cd-messenger affected?

Yes. 2.7.26, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does cd-messenger have?

1 vulnerability is recorded for cd-messenger in the npm ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new cd-messenger vulnerabilities disclosed?

0 vulnerabilities were recorded for cd-messenger in the last 12 months, and the oldest entry in this database dates to 17 May 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of cd-messenger are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.