VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ibm_db: vulnerability history, versions and safety

ibm_db is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 32 releases, from Feb 2019 to 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
2 vulnerabilities recorded 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 ibm_db vulnerabilities

Vulert verdict on ibm_db 4.1.0 i

Updated on 23 Oct 2026

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

Package health score 71/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 4.1.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 03 Sep 2020 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Depended on by 24 packages i
  • Stars 209 i
  • OpenSSF scorecard 2/10 i
  • Last release this month 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 ibm_db, 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
4.1.0 19 Oct 2026 none MIT — Details →
4.0.1 13 May 2026 none MIT — Details →
4.0.0 31 Mar 2026 none MIT — Details →
3.3.5 09 Mar 2026 none MIT — Details →
3.3.4 06 Oct 2025 none MIT — Details →
3.3.3 07 Sep 2025 none MIT — Details →
3.3.2 22 Jun 2025 none MIT — Details →
3.3.1 04 Jun 2025 none MIT — Details →
3.3.0 01 Dec 2024 none MIT — Details →
3.2.5 21 Nov 2024 none MIT — Details →
3.2.4 31 Mar 2024 none MIT — Details →
3.2.3 16 Nov 2023 none MIT — Details →
3.2.2 23 Sep 2023 none MIT — Details →
3.2.1 21 May 2023 none MIT — Details →
3.2.0 07 May 2023 none MIT — Details →
3.1.0 05 Dec 2022 none MIT — Details →
3.0.0 06 Sep 2022 none MIT — Details →
2.8.2 16 Jul 2022 none MIT — Details →
2.8.1 18 Dec 2021 none MIT — Details →
2.8.0 12 Sep 2021 none MIT — Details →
2.7.4 17 Jun 2021 none MIT — Details →
2.7.3 15 Mar 2021 none MIT — Details →
2.7.2 20 Jan 2021 none MIT — Details →
2.7.1 27 Aug 2020 none MIT — Details →
2.7.0 07 Jun 2020 none MIT — Details →
2.6.4 20 Feb 2020 none MIT — Details →
2.6.3 11 Dec 2019 none MIT — Details →
2.6.2 09 Dec 2019 none MIT — Details →
2.6.1 03 Sep 2019 none MIT — Details →
2.6.0 19 Aug 2019 none MIT — Details →
2.5.3 19 Jul 2019 M1 MIT Yes Details →
2.5.2 31 May 2019 M1 MIT Yes Details →
2.5.1 25 Apr 2019 M1 MIT Yes Details →
2.5.0 05 Dec 2018 M1 MIT Yes Details →
2.4.1 26 Sep 2018 M1 MIT Yes Details →
2.4.0 04 Jun 2018 M1 MIT Yes Details →
2.3.1 19 Apr 2018 M1 MIT Yes Details →
2.3.0 03 Apr 2018 M1 MIT Yes Details →
2.2.1 29 Sep 2017 M1 MIT Yes Details →
2.2.0 17 Sep 2017 M1 MIT Yes Details →
2.1.0 10 Jul 2017 M1 MIT Yes Details →
2.0.0 22 Feb 2017 M1 MIT Yes Details →
1.0.2 17 Jan 2017 M1 MIT Yes Details →
1.0.1 31 Oct 2016 H1 M1 MIT Yes Details →
1.0.0 08 Jul 2016 H1 M1 MIT Yes Details →
0.0.19 30 Jan 2016 H1 M1 MIT Yes Details →
0.0.18 28 Jan 2016 H1 M1 MIT Yes Details →
0.0.17 11 Jan 2016 H1 M1 MIT Yes Details →
0.0.16 05 Jan 2016 H1 M1 MIT Yes Details →
0.0.15 15 Sep 2015 H1 M1 MIT Yes Details →
0.0.14 11 Aug 2015 H1 M1 MIT Yes Details →
0.0.13 04 Aug 2015 H1 M1 MIT Yes Details →
0.0.12 30 Jul 2015 H1 M1 MIT Yes Details →
0.0.11 08 Jul 2015 H1 M1 MIT Yes Details →
0.0.10 29 Jun 2015 H1 M1 MIT Yes Details →
0.0.9 10 Jun 2015 H1 M1 MIT Yes Details →
0.0.8 23 Feb 2015 H1 M1 MIT Yes Details →
0.0.6 11 Dec 2014 H1 M1 MIT Yes Details →
0.0.5 10 Dec 2014 H1 M1 MIT Yes Details →
0.0.3 29 Oct 2014 H1 M1 MIT Yes Details →
0.0.2 27 Oct 2014 H1 M1 ISC Yes Details →
0.0.1 22 Jan 2014 H1 M1 MIT Yes 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

  • 2019 1
  • 2020 1

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 ibm_db

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-10577: Insecure Resource Download in ibm_db 8.1 high 1.0.2 18 Feb 2019
Sensitive Data Exposure in ibm_db 5.0 medium 2.6.0 03 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 ibm_db

Is ibm_db safe to use?

Vulert records 2 vulnerabilities for ibm_db in npm: 0 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 ibm_db's Vulert package health score?

Vulert scores ibm_db 71/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 ibm_db affected?

No. 4.1.0, 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 ibm_db have?

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

0 vulnerabilities were recorded for ibm_db 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 ibm_db 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 ibm_db for upcoming vulnerabilities?

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