VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

bson: vulnerability history, versions and safety

bson is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 23 releases, from Sep 2018 to Feb 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 H1 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 bson vulnerabilities

Vulert verdict on bson 7.3.3 i

Updated on 22 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 7.3.3 — unaffected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 10 Feb 2022 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 5,457 packages i
  • Stars 1,216 i
  • OpenSSF scorecard 5/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 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 bson, 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
7.3.3 15 Sep 2026 none Apache-2.0 — Details →
7.3.2 11 Aug 2026 none Apache-2.0 — Details →
7.3.1 24 Jun 2026 none Apache-2.0 — Details →
7.3.0 17 Jun 2026 none Apache-2.0 — Details →
7.2.0 03 Feb 2026 none Apache-2.0 — Details →
7.1.1 17 Jan 2026 none Apache-2.0 — Details →
7.1.0 16 Jan 2026 none Apache-2.0 — Details →
7.0.0 05 Nov 2025 none Apache-2.0 — Details →
7.0.0-alpha.2 24 Oct 2025 none Apache-2.0 — Details →
7.0.0-alpha.1 22 Oct 2025 none Apache-2.0 — Details →
7.0.0-alpha 21 Oct 2025 none Apache-2.0 — Details →
6.10.4 02 Jun 2025 none Apache-2.0 — Details →
6.9.1 06 Mar 2025 none Apache-2.0 — Details →
6.8.1 06 Mar 2025 none Apache-2.0 — Details →
6.7.1 06 Mar 2025 none Apache-2.0 — Details →
6.6.1 06 Mar 2025 none Apache-2.0 — Details →
6.5.1 06 Mar 2025 none Apache-2.0 — Details →
6.4.1 05 Mar 2025 none Apache-2.0 — Details →
6.10.3 19 Feb 2025 none Apache-2.0 — Details →
6.10.2 30 Jan 2025 none Apache-2.0 — Details →
6.10.1 03 Dec 2024 none Apache-2.0 — Details →
6.10.0 19 Nov 2024 none Apache-2.0 — Details →
6.9.0 21 Oct 2024 none Apache-2.0 — Details →
6.8.0 27 Jun 2024 none Apache-2.0 — Details →
6.7.0 02 May 2024 none Apache-2.0 — Details →
6.6.0 02 Apr 2024 none Apache-2.0 — Details →
6.5.0 12 Mar 2024 none Apache-2.0 — Details →
6.4.0 29 Feb 2024 none Apache-2.0 — Details →
6.3.0 01 Feb 2024 none Apache-2.0 — Details →
6.2.0 18 Oct 2023 none Apache-2.0 — Details →
5.5.1 18 Oct 2023 none Apache-2.0 — Details →
6.1.0 13 Sep 2023 none Apache-2.0 — Details →
5.5.0 13 Sep 2023 none Apache-2.0 — Details →
6.0.0 28 Aug 2023 none Apache-2.0 — Details →
6.0.0-alpha.1 24 Aug 2023 none Apache-2.0 — Details →
6.0.0-alpha 24 Aug 2023 none Apache-2.0 — Details →
6.0.0-alpha.0 15 Aug 2023 none Apache-2.0 — Details →
5.4.0 05 Jul 2023 none Apache-2.0 — Details →
5.3.0 10 May 2023 none Apache-2.0 — Details →
5.2.0 04 Apr 2023 none Apache-2.0 — Details →
5.1.0 16 Mar 2023 none Apache-2.0 — Details →
5.0.1 16 Feb 2023 none Apache-2.0 — Details →
5.0.0 31 Jan 2023 none Apache-2.0 — Details →
5.0.0-alpha.3 20 Jan 2023 none Apache-2.0 — Details →
5.0.0-alpha.2 10 Jan 2023 none Apache-2.0 — Details →
4.7.2 10 Jan 2023 none Apache-2.0 — Details →
4.7.1 05 Jan 2023 none Apache-2.0 — Details →
5.0.0-alpha.1 19 Dec 2022 none Apache-2.0 — Details →
5.0.0-alpha.0 19 Dec 2022 none Apache-2.0 — Details →
4.7.0 18 Aug 2022 none Apache-2.0 — Details →
4.6.5 07 Jul 2022 none Apache-2.0 — Details →
4.6.4 19 May 2022 none Apache-2.0 — Details →
4.6.3 20 Apr 2022 none Apache-2.0 — Details →
4.6.2 22 Mar 2022 none Apache-2.0 — Details →
4.6.1 06 Jan 2022 none Apache-2.0 — Details →
4.6.0 23 Nov 2021 none Apache-2.0 — Details →
4.5.4 03 Nov 2021 none Apache-2.0 — Details →
4.5.3 05 Oct 2021 none Apache-2.0 — Details →
4.5.2 14 Sep 2021 none Apache-2.0 — Details →
4.5.1 24 Aug 2021 none Apache-2.0 — Details →
4.5.0 19 Aug 2021 none Apache-2.0 — Details →
4.4.1 06 Jul 2021 none Apache-2.0 — Details →
4.4.0 18 May 2021 none Apache-2.0 — Details →
4.3.0 06 Apr 2021 none Apache-2.0 — Details →
1.1.6 16 Mar 2021 none Apache-2.0 — Details →
4.2.3 02 Mar 2021 none Apache-2.0 — Details →
4.2.2 01 Dec 2020 none Apache-2.0 — Details →
4.2.1 01 Dec 2020 none Apache-2.0 — Details →
4.2.0 13 Oct 2020 none Apache-2.0 — Details →
1.1.5 10 Aug 2020 none Apache-2.0 — Details →
4.1.0 10 Aug 2020 none Apache-2.0 — Details →
4.0.4 26 Mar 2020 none Apache-2.0 — Details →
1.1.4 24 Mar 2020 none Apache-2.0 — Details →
4.0.3 09 Jan 2020 none Apache-2.0 — Details →
1.1.3 09 Nov 2019 C1 M1 Apache-2.0 Yes Details →
1.1.2 08 Nov 2019 C1 M1 Apache-2.0 Yes Details →
1.1.1 08 Mar 2019 C1 M1 Apache-2.0 Yes Details →
4.0.2 08 Mar 2019 none Apache-2.0 — Details →
4.0.1 06 Dec 2018 none Apache-2.0 — Details →
4.0.0 13 Nov 2018 none Apache-2.0 — Details →
4.0.0-rc8 07 Nov 2018 none Apache-2.0 — Details →
4.0.0-rc7 23 Oct 2018 none Apache-2.0 — Details →
4.0.0-rc6 23 Oct 2018 none Apache-2.0 — Details →
4.0.0-rc5 12 Oct 2018 none Apache-2.0 — Details →
4.0.0-rc4 12 Oct 2018 none Apache-2.0 — Details →
4.0.0-rc3 10 Oct 2018 none Apache-2.0 — Details →
4.0.0-rc2 03 Oct 2018 none Apache-2.0 — Details →
4.0.0-rc1 27 Sep 2018 none Apache-2.0 — Details →
1.1.0 13 Aug 2018 C1 M1 Apache-2.0 Yes Details →
3.0.2 13 Jul 2018 none Apache-2.0 — Details →
3.0.1 12 Jul 2018 none Apache-2.0 — Details →
3.0.0 13 Jun 2018 none Apache-2.0 — Details →
1.0.9 07 Jun 2018 C1 M1 Apache-2.0 Yes Details →
1.0.8 07 Jun 2018 C1 M1 Apache-2.0 Yes Details →
2.0.8 06 Jun 2018 none Apache-2.0 — Details →
1.0.7 06 Jun 2018 C1 M1 Apache-2.0 Yes Details →
2.0.7 31 May 2018 none Apache-2.0 — Details →
2.0.6 27 Apr 2018 none Apache-2.0 — Details →
2.0.5 06 Apr 2018 none Apache-2.0 — Details →
2.0.4 12 Mar 2018 none Apache-2.0 — Details →
2.0.3 12 Mar 2018 none — — Details →
1.0.6 12 Mar 2018 C1 M1 — Yes Details →
2.0.2 02 Mar 2018 none — — Details →
2.0.1 28 Feb 2018 none — — Details →
1.0.5 26 Feb 2018 C1 M1 — Yes Details →
2.0.0 26 Feb 2018 none — — Details →
1.0.4 11 Jan 2017 C1 H1 M1 — Yes Details →
1.0.3 03 Jan 2017 C1 H1 M1 — Yes Details →
1.0.2 02 Jan 2017 C1 H1 M1 — Yes Details →
1.0.1 07 Dec 2016 C1 H1 M1 — Yes Details →
1.0.0 05 Dec 2016 C1 H1 M1 — Yes Details →
0.5.7 18 Nov 2016 C1 H1 M1 — Yes Details →
0.5.6 19 Oct 2016 C1 H1 M1 — Yes Details →
0.5.5 15 Sep 2016 C1 H1 M1 — Yes Details →
0.5.4 23 Aug 2016 C1 H1 M1 — Yes Details →
0.5.3 16 Aug 2016 C1 H1 M1 — Yes Details →
0.5.2 11 Jul 2016 C1 H1 M1 — Yes Details →
0.5.1 11 Jul 2016 C1 H1 M1 — Yes Details →
0.5.0 05 Jul 2016 C1 H1 M1 — Yes Details →
0.4.23 08 Apr 2016 C1 M1 — Yes Details →

The newest 120 of 185 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2021 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for bson

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7610: Deserialization of Untrusted Data in bson 9.8 critical 1.1.4 07 May 2021
CVE-2018-13863: Vulnerability in bson package 7.5 high 1.0.5 17 Sep 2018
CVE-2019-2391: Deserialization of Untrusted Data in bson 5.4 medium 1.1.4 10 Feb 2022

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 bson

Is bson safe to use?

Vulert records 3 vulnerabilities for bson in npm: 1 critical, 1 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 bson's Vulert package health score?

Vulert scores bson 80/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 bson affected?

No. 7.3.3, 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 bson should I use?

7.3.3 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 bson have?

3 vulnerabilities are recorded for bson in the npm ecosystem: 1 critical, 1 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 bson vulnerabilities disclosed?

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

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