VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

gitbook: vulnerability history, versions and safety

gitbook is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Sep 2020 to May 2022. 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 M2
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 gitbook vulnerabilities

Vulert verdict on gitbook 2.6.9 i

Updated on 23 Oct 2026

Careful: 2.6.9 has 2 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Moderate

The registry marks the latest release as deprecated, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.6.9 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 1 i
  • Depended on by 27 packages i
  • Stars 29,069 i
  • OpenSSF scorecard 3/10 i
  • Last release 96 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 gitbook, 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
2.6.9 11 Oct 2018 M2 Apache-2.0 No Details →
2.6.8 10 Oct 2018 M2 Apache-2.0 No Details →
3.2.3 03 Aug 2017 M1 Apache-2.0 No Details →
4.0.0-alpha.6 16 Mar 2017 M1 Apache-2.0 No Details →
4.0.0-alpha.5 09 Mar 2017 M1 Apache-2.0 No Details →
4.0.0-alpha.4 27 Jan 2017 M1 Apache-2.0 No Details →
4.0.0-alpha.3 13 Jan 2017 M1 Apache-2.0 No Details →
4.0.0-alpha.2 13 Jan 2017 M1 Apache-2.0 No Details →
4.0.0-alpha.1 13 Jan 2017 M1 Apache-2.0 No Details →
3.2.2 01 Oct 2016 M1 Apache-2.0 No Details →
3.2.1 28 Sep 2016 M2 Apache-2.0 No Details →
3.2.0 11 Jul 2016 M2 Apache-2.0 No Details →
3.2.0-pre.1 05 Jul 2016 M2 Apache-2.0 No Details →
3.2.0-pre.0 30 Jun 2016 M2 Apache-2.0 No Details →
3.1.1 10 Jun 2016 M2 Apache-2.0 No Details →
3.1.0 06 Jun 2016 M2 Apache-2.0 No Details →
3.0.3 27 May 2016 M2 Apache-2.0 No Details →
3.0.2 25 May 2016 M2 Apache-2.0 No Details →
3.0.1 25 May 2016 M2 Apache-2.0 No Details →
3.0.0 20 May 2016 M2 Apache-2.0 No Details →
3.0.0-pre.15 12 May 2016 M2 Apache-2.0 No Details →
3.0.0-pre.14 10 May 2016 M2 Apache-2.0 No Details →
3.0.0-pre.13 06 May 2016 M2 Apache-2.0 No Details →
3.0.0-pre.12 04 May 2016 M2 Apache-2.0 No Details →
3.0.0-pre.11 03 May 2016 M2 Apache-2.0 No Details →
3.0.0-pre.10 02 May 2016 M2 Apache-2.0 No Details →
3.0.0-pre.9 19 Apr 2016 M2 Apache-2.0 No Details →
3.0.0-pre.8 14 Apr 2016 M2 Apache-2.0 No Details →
3.0.0-pre.7 11 Apr 2016 M2 Apache-2.0 No Details →
3.0.0-pre.6 08 Apr 2016 M2 Apache-2.0 No Details →
3.0.0-pre.5 07 Mar 2016 M2 Apache-2.0 No Details →
3.0.0-pre.4 07 Mar 2016 M2 Apache-2.0 No Details →
3.0.0-pre.3 02 Mar 2016 M2 Apache-2.0 No Details →
3.0.0-pre.2 29 Feb 2016 M2 Apache-2.0 No Details →
3.0.0-pre.1 26 Feb 2016 M2 Apache-2.0 No Details →
2.6.7 13 Jan 2016 M2 Apache-2.0 No Details →
2.6.6 16 Dec 2015 M2 Apache-2.0 No Details →
2.6.5 11 Dec 2015 M2 Apache-2.0 No Details →
2.6.4 02 Dec 2015 M2 Apache-2.0 No Details →
2.6.3 02 Dec 2015 M2 Apache-2.0 No Details →
2.6.2 25 Nov 2015 M2 Apache-2.0 No Details →
2.6.1 25 Nov 2015 M2 Apache-2.0 No Details →
2.6.0 25 Nov 2015 M2 Apache-2.0 No Details →
2.5.2 03 Nov 2015 M2 Apache-2.0 No Details →
2.5.1 27 Oct 2015 M2 Apache-2.0 No Details →
2.5.0 27 Oct 2015 M2 Apache-2.0 No Details →
2.5.0-beta.7 22 Oct 2015 M2 Apache-2.0 No Details →
2.5.0-beta.6 20 Oct 2015 M2 Apache-2.0 No Details →
2.5.0-beta.5 16 Oct 2015 M2 Apache-2.0 No Details →
2.5.0-beta.4 14 Oct 2015 M2 Apache-2.0 No Details →
2.5.0-beta.3 14 Oct 2015 M2 Apache-2.0 No Details →
2.5.0-beta.2 14 Oct 2015 M2 Apache-2.0 No Details →
2.5.0-beta.1 13 Oct 2015 M2 Apache-2.0 No Details →
2.4.3 01 Oct 2015 M2 Apache-2.0 No Details →
2.4.2 22 Sep 2015 M2 Apache-2.0 No Details →
2.4.1 18 Sep 2015 M2 Apache-2.0 No Details →
2.4.0 15 Sep 2015 M2 Apache-2.0 No Details →
2.3.3 10 Sep 2015 M2 Apache-2.0 No Details →
2.3.2 09 Sep 2015 M2 Apache-2.0 No Details →
2.3.1 08 Sep 2015 M2 Apache-2.0 No Details →
2.3.0 01 Sep 2015 M2 Apache-2.0 No Details →
2.2.0 28 Jul 2015 M2 Apache-2.0 No Details →
2.1.0 02 Jun 2015 M2 Apache-2.0 No Details →
2.0.4 28 May 2015 M2 Apache-2.0 No Details →
2.0.3 27 May 2015 M2 Apache-2.0 No Details →
2.0.2 02 May 2015 M2 Apache-2.0 No Details →
2.0.1 02 Apr 2015 M2 Apache-2.0 No Details →
2.0.0 25 Mar 2015 M2 Apache-2.0 No Details →
2.0.0-beta.5 17 Mar 2015 M2 Apache-2.0 No Details →
2.0.0-beta.4 17 Mar 2015 M2 Apache-2.0 No Details →
2.0.0-beta.3 12 Mar 2015 M2 Apache-2.0 No Details →
2.0.0-beta.2 11 Mar 2015 M2 Apache-2.0 No Details →
2.0.0-beta.1 11 Mar 2015 M2 Apache-2.0 No Details →
2.0.0-alpha.9 24 Feb 2015 M2 Apache-2.0 No Details →
2.0.0-alpha.8 14 Feb 2015 M2 Apache-2.0 No Details →
2.0.0-alpha.7 12 Feb 2015 M2 Apache-2.0 No Details →
2.0.0-alpha.6 06 Feb 2015 M2 Apache-2.0 No Details →
2.0.0-alpha.5 05 Feb 2015 M2 Apache-2.0 No Details →
2.0.0-alpha.4 04 Feb 2015 M2 Apache-2.0 No Details →
2.0.0-alpha.3 04 Feb 2015 M2 Apache-2.0 No Details →
2.0.0-alpha.2 04 Feb 2015 M2 Apache-2.0 No Details →
2.0.0-alpha.1 03 Feb 2015 M2 Apache-2.0 No Details →
1.5.0 17 Dec 2014 M2 Apache-2.0 No Details →
1.4.2 10 Dec 2014 M2 Apache-2.0 No Details →
1.4.1 30 Nov 2014 M2 Apache-2.0 No Details →
1.4.0 30 Nov 2014 M2 Apache-2.0 No Details →
1.3.4 25 Nov 2014 M2 Apache-2.0 No Details →
1.3.3 14 Nov 2014 M2 Apache-2.0 No Details →
1.3.2 14 Nov 2014 M2 Apache-2.0 No Details →
1.3.1 03 Nov 2014 M2 Apache-2.0 No Details →
1.3.0 01 Nov 2014 M2 Apache-2.0 No Details →
1.2.0 30 Oct 2014 M2 Apache-2.0 No Details →
1.1.1 13 Oct 2014 M2 Apache-2.0 No Details →
1.1.0 24 Sep 2014 M2 Apache-2.0 No Details →
1.0.3 05 Sep 2014 M2 Apache-2.0 No Details →
1.0.2 21 Aug 2014 M2 Apache-2.0 No Details →
1.0.1 20 Aug 2014 M2 Apache-2.0 No Details →
1.0.0 19 Aug 2014 M2 Apache-2.0 No Details →
0.7.1 08 Aug 2014 M2 Apache-2.0 No Details →
0.7.0 01 Aug 2014 M2 Apache-2.0 No Details →
0.6.3 30 Jul 2014 M2 — No Details →
0.6.2 30 Jul 2014 M2 — No Details →
0.6.1 23 Jul 2014 M2 — No Details →
0.6.0 12 Jul 2014 M2 — No Details →
0.5.6 24 Jun 2014 M2 — No Details →
0.5.5 18 Jun 2014 M2 — No Details →
0.5.4 17 Jun 2014 M2 — No Details →
0.5.3 16 Jun 2014 M2 — No Details →
0.5.2 07 Jun 2014 M2 — No Details →
0.5.1 07 Jun 2014 M2 — No Details →
0.5.0 03 Jun 2014 M2 — No Details →
0.4.8 29 May 2014 M2 — No Details →
0.4.7 26 May 2014 M2 — No Details →
0.4.6 23 May 2014 M2 — No Details →
0.4.5 21 May 2014 M2 — No Details →
0.4.4 21 May 2014 M2 — No Details →
0.4.3 18 May 2014 M2 — No Details →
0.4.2 01 May 2014 M2 — No Details →
0.4.1 29 Apr 2014 M2 — No Details →
0.4.0 28 Apr 2014 M2 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 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 gitbook

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2017-16019: Cross-Site Scripting in gitbook 6.1 medium 3.2.2 01 Sep 2020
CVE-2019-19596: Cross-site Scripting in GitBook 5.4 medium No fix published 24 May 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: 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 gitbook

Is gitbook safe to use?

Vulert records 2 vulnerabilities for gitbook in npm: 0 critical, 0 high, 2 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is gitbook's Vulert package health score?

Vulert scores gitbook 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of gitbook affected?

Yes. 2.6.9, the version you would install today, has 2 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of gitbook should I use?

2.6.9 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 gitbook have?

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

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

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