VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mqtt-packet: vulnerability history, versions and safety

mqtt-packet is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 22 releases, from Feb 2019 to May 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 mqtt-packet vulnerabilities

Vulert verdict on mqtt-packet 9.0.2 i

Updated on 23 Oct 2026

Good news: 9.0.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 70/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

What to do: Stay on 9.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 9.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 9.0.2 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 14 May 2019 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 2,124 packages i
  • Stars 216 i
  • OpenSSF scorecard 3/10 i
  • Last release 19 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 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 mqtt-packet, 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
9.0.2 04 Mar 2025 none MIT — Details →
9.0.1 12 Nov 2024 none MIT — Details →
9.0.0 08 Nov 2023 none MIT — Details →
8.2.1 04 Oct 2023 none MIT — Details →
8.2.0 07 Jul 2023 none MIT — Details →
8.1.2 10 Aug 2022 none MIT — Details →
8.1.1 21 Jul 2022 none MIT — Details →
8.1.0 18 Jul 2022 none MIT — Details →
8.0.0 21 Feb 2022 none MIT — Details →
7.1.2 03 Feb 2022 none MIT — Details →
7.1.1 21 Sep 2021 none MIT — Details →
7.1.0 07 Sep 2021 none MIT — Details →
7.0.0 07 Jun 2021 none MIT — Details →
6.10.0 14 May 2021 none MIT — Details →
6.9.1 16 Apr 2021 none MIT — Details →
6.9.0 22 Feb 2021 none MIT — Details →
6.8.1 19 Feb 2021 none MIT — Details →
6.8.0 12 Feb 2021 none MIT — Details →
6.7.0 05 Dec 2020 none MIT — Details →
6.6.0 08 Sep 2020 none MIT — Details →
6.5.0 31 Aug 2020 none MIT — Details →
6.4.0 24 Aug 2020 none MIT — Details →
6.3.2 03 Mar 2020 none MIT — Details →
6.3.1 17 Feb 2020 none MIT — Details →
6.3.0 29 Nov 2019 none MIT — Details →
6.2.1 28 Jul 2019 none MIT — Details →
6.2.0 06 Jul 2019 none MIT — Details →
3.5.1 17 Apr 2019 none MIT — Details →
4.1.3 17 Apr 2019 none MIT — Details →
5.6.1 17 Apr 2019 none MIT — Details →
6.1.2 17 Apr 2019 none MIT — Details →
6.1.1 21 Mar 2019 none MIT — Details →
6.1.0 20 Mar 2019 none MIT — Details →
6.0.0 03 Jun 2018 none MIT — Details →
5.6.0 11 May 2018 none MIT — Details →
3.5.0 02 Mar 2018 H1 MIT Yes Details →
5.5.0 21 Feb 2018 none MIT — Details →
5.4.0 21 Jun 2017 none MIT — Details →
5.3.0 07 Apr 2017 none MIT — Details →
5.2.2 16 Mar 2017 none MIT — Details →
3.4.8 13 Jan 2017 H1 MIT Yes Details →
5.2.1 19 Dec 2016 none MIT — Details →
5.2.0 21 Sep 2016 none MIT — Details →
5.1.0 13 Sep 2016 none MIT — Details →
5.0.0 07 Sep 2016 none MIT — Details →
3.4.7 06 Jun 2016 H1 MIT Yes Details →
4.1.2 06 Jun 2016 none MIT — Details →
4.1.1 14 Mar 2016 none MIT — Details →
4.1.0 26 Jan 2016 none MIT — Details →
3.4.6 15 Jan 2016 H1 MIT Yes Details →
4.0.5 15 Jan 2016 none MIT — Details →
3.4.5 15 Jan 2016 H2 MIT Yes Details →
4.0.4 15 Jan 2016 none MIT — Details →
4.0.3 22 Oct 2015 none MIT — Details →
4.0.2 22 Oct 2015 none MIT — Details →
4.0.1 21 Oct 2015 none MIT — Details →
4.0.0 21 Oct 2015 none MIT — Details →
3.4.4 15 Oct 2015 H2 MIT Yes Details →
3.4.3 08 Oct 2015 H2 MIT Yes Details →
3.4.2 08 Oct 2015 H2 MIT Yes Details →
3.4.1 13 Sep 2015 H2 MIT Yes Details →
3.4.0 13 Sep 2015 H2 MIT Yes Details →
3.3.1 01 Sep 2015 H2 MIT Yes Details →
3.3.0 17 Jul 2015 H2 MIT Yes Details →
3.2.0 18 Jan 2015 H2 MIT Yes Details →
3.1.1 13 Jan 2015 H2 MIT Yes Details →
3.1.0 12 Jan 2015 H2 MIT Yes Details →
3.0.0 09 Jan 2015 H2 MIT Yes Details →
2.0.1 08 Jan 2015 H2 MIT Yes Details →
2.0.0 17 Dec 2014 H2 MIT Yes Details →
1.0.3 11 Nov 2014 H2 MIT Yes Details →
1.0.2 01 Nov 2014 H2 MIT Yes Details →
1.0.1 31 Oct 2014 H2 MIT Yes Details →
1.0.0 31 Oct 2014 H2 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 2

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

03 Vulnerabilities

Recorded vulnerabilities for mqtt-packet

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-5432: Improper Input Validation and Buffer Over-read in mqtt-packet 7.5 high 3.5.1 14 May 2019
CVE-2016-10523: Denial of Service in mqtt-packet N/A high 3.4.6 18 Feb 2019

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 mqtt-packet

Is mqtt-packet safe to use?

Vulert records 2 vulnerabilities for mqtt-packet in npm: 0 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is mqtt-packet's Vulert package health score?

Vulert scores mqtt-packet 70/100, which reads as in good shape. 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).

Is the latest version of mqtt-packet affected?

No. 9.0.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of mqtt-packet should I use?

9.0.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does mqtt-packet have?

2 vulnerabilities are recorded for mqtt-packet in the npm ecosystem: 0 critical, 2 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 mqtt-packet vulnerabilities disclosed?

0 vulnerabilities were recorded for mqtt-packet in the last 12 months, and the oldest entry in this database dates to 18 Feb 2019. 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 mqtt-packet 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 mqtt-packet for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mqtt-packet version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.