VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

converse.js: vulnerability history, versions and safety

converse.js is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 6 releases, first recorded in Sep 2020. 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 M1
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 converse.js vulnerabilities

Vulert verdict on converse.js 14.0.1 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 14.0.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 11 Sep 2020 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Stars 3,301 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MPL-2.0 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 converse.js, 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
14.0.1 17 Oct 2026 none MPL-2.0 — Details →
14.0.0 26 Jun 2026 none MPL-2.0 — Details →
14.0.0-beta.4 22 Jun 2026 none MPL-2.0 — Details →
14.0.0-beta.3 19 Jun 2026 none MPL-2.0 — Details →
14.0.0-beta.2 18 Jun 2026 none MPL-2.0 — Details →
14.0.0-beta.1 18 Jun 2026 none MPL-2.0 — Details →
13.0.1 27 May 2026 none MPL-2.0 — Details →
13.0.0 20 May 2026 none MPL-2.0 — Details →
12.0.0 28 Aug 2025 none MPL-2.0 — Details →
11.0.1 09 Jun 2025 none MPL-2.0 — Details →
11.0.0 21 May 2025 none MPL-2.0 — Details →
10.1.8 17 Dec 2024 none MPL-2.0 — Details →
10.1.7 15 Mar 2024 none MPL-2.0 — Details →
10.1.6 31 Aug 2023 none MPL-2.0 — Details →
10.1.5 30 Jun 2023 none MPL-2.0 — Details →
10.1.4 25 Jun 2023 none MPL-2.0 — Details →
10.1.3 23 Jun 2023 none MPL-2.0 — Details →
10.1.2 17 Feb 2023 none MPL-2.0 — Details →
10.1.1 15 Feb 2023 none MPL-2.0 — Details →
10.1.0 07 Jan 2023 none MPL-2.0 — Details →
10.0.0 01 Nov 2022 none MPL-2.0 — Details →
9.1.1 05 May 2022 none MPL-2.0 — Details →
9.1.0 02 Apr 2022 none MPL-2.0 — Details →
9.0.0 29 Nov 2021 none MPL-2.0 — Details →
8.0.1 09 Sep 2021 none MPL-2.0 — Details →
8.0.0 04 Sep 2021 none MPL-2.0 — Details →
7.0.6 11 Jun 2021 none MPL-2.0 — Details →
7.0.5 16 Mar 2021 none MPL-2.0 — Details →
7.0.4 09 Dec 2020 none MPL-2.0 — Details →
7.0.3 02 Dec 2020 none MPL-2.0 — Details →
7.0.2 23 Nov 2020 none MPL-2.0 — Details →
7.0.1 19 Nov 2020 none MPL-2.0 — Details →
7.0.0 18 Nov 2020 none MPL-2.0 — Details →
6.0.1 13 Feb 2020 none MPL-2.0 — Details →
5.0.5 20 Nov 2019 none MPL-2.0 — Details →
5.0.3 13 Sep 2019 none MPL-2.0 — Details →
5.0.2 11 Sep 2019 none MPL-2.0 — Details →
5.0.1 14 Aug 2019 none MPL-2.0 — Details →
5.0.0 08 Aug 2019 none MPL-2.0 — Details →
4.2.0 04 Apr 2019 none MPL-2.0 — Details →
4.1.2 22 Feb 2019 none MPL-2.0 — Details →
4.1.1 18 Feb 2019 none MPL-2.0 — Details →
4.1.0 11 Jan 2019 none MPL-2.0 — Details →
4.0.6 07 Dec 2018 none MPL-2.0 — Details →
4.0.5 15 Nov 2018 none MPL-2.0 — Details →
4.0.4 29 Oct 2018 none MPL-2.0 — Details →
4.0.3 22 Oct 2018 none MPL-2.0 — Details →
4.0.2 02 Oct 2018 none MPL-2.0 — Details →
4.0.1 19 Sep 2018 none MPL-2.0 — Details →
4.0.0 07 Sep 2018 none MPL-2.0 — Details →
3.3.4 05 Mar 2018 none MPL-2.0 — Details →
3.3.3 14 Feb 2018 none MPL-2.0 — Details →
3.3.2 29 Jan 2018 none MPL-2.0 — Details →
3.3.1 18 Jan 2018 none MPL-2.0 — Details →
3.3.0 17 Jan 2018 none MPL-2.0 — Details →
3.2.1 29 Aug 2017 none MPL-2.0 — Details →
3.2.0 09 Aug 2017 none MPL-2.0 — Details →
3.1.1 12 Jul 2017 none MPL-2.0 — Details →
3.1.0 05 Jul 2017 none MPL-2.0 — Details →
3.0.2 23 Apr 2017 none MPL-2.0 — Details →
3.0.1 04 Apr 2017 none MPL-2.0 — Details →
3.0.0 05 Mar 2017 none MPL-2.0 — Details →
2.0.6 13 Feb 2017 none MPL-2.0 — Details →
1.0.7 01 Feb 2017 none MPL-2.0 — Details →
2.0.5 01 Feb 2017 none MPL-2.0 — Details →
2.0.4 13 Dec 2016 none MPL-2.0 — Details →
2.0.3 30 Nov 2016 none MPL-2.0 — Details →
2.0.2 30 Nov 2016 none MPL-2.0 — Details →
2.0.1 07 Nov 2016 none MPL-2.0 — Details →
2.0.0 16 Sep 2016 none MPL-2.0 — Details →
1.0.6 12 Aug 2016 M1 MPL-2.0 Yes Details →
1.0.5 28 Jul 2016 M1 MPL-2.0 Yes Details →
1.0.4 26 Jul 2016 M1 MPL-2.0 Yes Details →
1.0.3 20 Jun 2016 M1 MPL-2.0 Yes Details →
1.0.2 25 May 2016 M1 MPL-2.0 Yes Details →
1.0.0 20 May 2016 M1 MPL-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 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 converse.js

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-5858: User Impersonation in converse.js 5.9 medium 1.0.7 11 Sep 2020

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 converse.js

Is converse.js safe to use?

Vulert records 1 vulnerabilities for converse.js in npm: 0 critical, 0 high, 1 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 converse.js's Vulert package health score?

Vulert scores converse.js 79/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 converse.js affected?

No. 14.0.1, 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.

How many vulnerabilities does converse.js have?

1 vulnerability is recorded for converse.js in the npm ecosystem: 0 critical, 0 high, 1 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 converse.js vulnerabilities disclosed?

0 vulnerabilities were recorded for converse.js in the last 12 months, and the oldest entry in this database dates to 11 Sep 2020. 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 converse.js 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 converse.js for upcoming vulnerabilities?

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