VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pouchdb: vulnerability history, versions and safety

pouchdb is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 66 releases, first recorded in Jul 2018. 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
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 pouchdb vulnerabilities

Vulert verdict on pouchdb 9.0.0 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Moderate

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

  • Current release 9.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 26 Jul 2018 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 97 packages i
  • Stars 17,617 i
  • OpenSSF scorecard 4/10 i
  • Last release 28 months 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 pouchdb, 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.0 21 Jun 2024 none Apache-2.0 — Details →
8.0.1 09 Feb 2023 none Apache-2.0 — Details →
8.0.0 15 Dec 2022 none Apache-2.0 — Details →
7.3.1 11 Nov 2022 none Apache-2.0 — Details →
7.3.0 13 Apr 2022 none Apache-2.0 — Details →
7.2.2 27 Jul 2020 none Apache-2.0 — Details →
7.2.1 16 Feb 2020 none Apache-2.0 — Details →
7.2.0 16 Feb 2020 none Apache-2.0 — Details →
7.1.1 14 Jun 2019 none Apache-2.0 — Details →
7.1.0 13 Jun 2019 none Apache-2.0 — Details →
7.0.0 21 Jun 2018 none Apache-2.0 — Details →
6.4.3 02 Feb 2018 none Apache-2.0 — Details →
6.4.2 24 Jan 2018 none Apache-2.0 — Details →
6.4.1 18 Dec 2017 none Apache-2.0 — Details →
6.4.0 17 Dec 2017 none Apache-2.0 — Details →
6.3.4 15 Jul 2017 none Apache-2.0 — Details →
6.3.3 14 Jul 2017 none Apache-2.0 — Details →
6.3.2 13 Jul 2017 none Apache-2.0 — Details →
6.3.1 13 Jul 2017 none Apache-2.0 — Details →
6.3.0 13 Jul 2017 none Apache-2.0 — Details →
6.2.1-prerelease 13 Jul 2017 none Apache-2.0 — Details →
6.2.0 20 Apr 2017 none Apache-2.0 — Details →
6.1.2 07 Feb 2017 none Apache-2.0 — Details →
6.1.1 05 Jan 2017 none Apache-2.0 — Details →
6.1.0 12 Dec 2016 none Apache-2.0 — Details →
6.0.7 15 Oct 2016 none Apache-2.0 — Details →
6.0.6 30 Sep 2016 none Apache-2.0 — Details →
6.0.5 17 Sep 2016 none Apache-2.0 — Details →
6.0.4 05 Sep 2016 C1 Apache-2.0 Yes Details →
6.0.3 05 Sep 2016 C1 Apache-2.0 Yes Details →
6.0.2 04 Sep 2016 C1 Apache-2.0 Yes Details →
6.0.1 03 Sep 2016 C1 Apache-2.0 Yes Details →
6.0.0 03 Sep 2016 C1 Apache-2.0 Yes Details →
5.4.5 03 Jul 2016 C1 Apache-2.0 Yes Details →
5.4.4 16 Jun 2016 C1 Apache-2.0 Yes Details →
5.4.3 13 Jun 2016 C1 Apache-2.0 Yes Details →
5.4.2 12 Jun 2016 C1 Apache-2.0 Yes Details →
5.4.1 08 Jun 2016 C1 Apache-2.0 Yes Details →
5.4.0 06 Jun 2016 C1 Apache-2.0 Yes Details →
5.3.2 21 Apr 2016 C1 Apache-2.0 Yes Details →
5.3.1 17 Mar 2016 C1 Apache-2.0 Yes Details →
5.3.0 04 Mar 2016 C1 Apache-2.0 Yes Details →
5.2.1 29 Jan 2016 C1 Apache-2.0 Yes Details →
5.2.0 13 Jan 2016 C1 Apache-2.0 Yes Details →
5.1.0 03 Nov 2015 C1 Apache-2.0 Yes Details →
5.0.0 06 Oct 2015 C1 Apache-2.0 Yes Details →
4.0.3 16 Sep 2015 C1 Apache-2.0 Yes Details →
4.0.2 12 Sep 2015 C1 Apache-2.0 Yes Details →
4.0.1 01 Sep 2015 C1 Apache-2.0 Yes Details →
4.0.0 03 Aug 2015 C1 Apache-2.0 Yes Details →
3.6.0 01 Jun 2015 C1 Apache-2.0 Yes Details →
3.5.0 07 May 2015 C1 Apache-2.0 Yes Details →
3.4.0 07 Apr 2015 C1 Apache-2.0 Yes Details →
3.3.1 14 Feb 2015 C1 Apache-2.0 Yes Details →
3.3.0 03 Feb 2015 C1 Apache-2.0 Yes Details →
3.2.1 05 Jan 2015 C1 Apache-2.0 Yes Details →
3.2.0 04 Dec 2014 C1 Apache-2.0 Yes Details →
3.1.0 10 Nov 2014 C1 Apache-2.0 Yes Details →
3.0.6 23 Sep 2014 C1 Apache-2.0 Yes Details →
3.0.5 07 Sep 2014 C1 Apache-2.0 Yes Details →
3.0.4 05 Sep 2014 C1 Apache-2.0 Yes Details →
3.0.3 30 Aug 2014 C1 Apache-2.0 Yes Details →
3.0.2 21 Aug 2014 C1 Apache-2.0 Yes Details →
3.0.1 16 Aug 2014 C1 Apache-2.0 Yes Details →
3.0.0 12 Aug 2014 C1 Apache-2.0 Yes Details →
2.2.3 31 May 2014 C1 Apache-2.0 Yes Details →
2.2.2 18 May 2014 C1 Apache-2.0 Yes Details →
2.2.1 16 May 2014 C1 Apache-2.0 Yes Details →
2.2.0 01 May 2014 C1 Apache-2.0 Yes Details →
2.0.2 14 Apr 2014 C1 Apache-2.0 Yes Details →
2.1.2 04 Apr 2014 C1 Apache-2.0 Yes Details →
2.1.1 04 Apr 2014 C1 Apache-2.0 Yes Details →
2.1.0 01 Apr 2014 C1 Apache-2.0 Yes Details →
2.0.1 08 Mar 2014 C1 Apache-2.0 Yes Details →
2.0.0 01 Mar 2014 C1 Apache-2.0 Yes Details →
1.1.0 02 Jan 2014 C1 Apache-2.0 Yes Details →
1.0.0 06 Dec 2013 C1 Apache-2.0 Yes Details →
0.0.18 05 Dec 2013 C1 Apache-2.0 Yes Details →
0.0.0 05 Dec 2013 C1 Apache-2.0 Yes Details →
0.0.16 01 Dec 2013 C1 Apache-2.0 Yes Details →
0.0.15 01 Dec 2013 C1 Apache-2.0 Yes Details →
0.0.14 22 Jul 2013 C1 Apache-2.0 Yes Details →
0.0.13 29 May 2013 C1 Apache-2.0 Yes Details →
0.0.12 18 Apr 2013 C1 Apache-2.0 Yes Details →
0.0.11 16 Apr 2013 C1 Apache-2.0 Yes Details →
0.0.10 22 Feb 2013 C1 Apache-2.0 Yes Details →
0.0.9 09 Feb 2013 C1 Apache-2.0 Yes Details →
0.0.8 09 Dec 2012 C1 Apache-2.0 Yes Details →
0.0.7 20 Nov 2012 C1 Apache-2.0 Yes Details →
0.0.6 12 Nov 2012 C1 Apache-2.0 Yes Details →
0.0.5 07 Nov 2012 C1 Apache-2.0 Yes Details →
0.0.4 01 Nov 2012 C1 Apache-2.0 Yes Details →
0.0.3 01 Nov 2012 C1 Apache-2.0 Yes Details →
0.0.2 25 Oct 2012 C1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 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 pouchdb

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-10546: Arbitrary Code Injection in pouchdb N/A critical 6.0.5 26 Jul 2018

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 pouchdb

Is pouchdb safe to use?

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

Vulert scores pouchdb 75/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 pouchdb affected?

No. 9.0.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.

Which version of pouchdb should I use?

9.0.0 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 pouchdb have?

1 vulnerability is recorded for pouchdb 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 pouchdb vulnerabilities disclosed?

0 vulnerabilities were recorded for pouchdb in the last 12 months, and the oldest entry in this database dates to 26 Jul 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 pouchdb 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 pouchdb for upcoming vulnerabilities?

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