VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mapbox.js: vulnerability history, versions and safety

mapbox.js is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 36 releases, first recorded in Nov 2018. 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
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 mapbox.js vulnerabilities

Vulert verdict on mapbox.js 3.3.1 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

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

  • Current release 3.3.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 09 Nov 2018 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 19 packages i
  • Stars 1,902 i
  • OpenSSF scorecard 3/10 i
  • Last release 77 months ago i
  • Licence BSD-3-Clause 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 mapbox.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
3.3.1 01 May 2020 none BSD-3-Clause — Details →
3.3.0 23 Mar 2020 none BSD-3-Clause — Details →
3.2.1 17 Oct 2019 none BSD-3-Clause — Details →
3.2.0 27 Feb 2019 none BSD-3-Clause — Details →
3.1.1 23 May 2017 none BSD-3-Clause — Details →
3.1.0 19 Apr 2017 none BSD-3-Clause — Details →
3.0.1 21 Nov 2016 none BSD-3-Clause — Details →
3.0.0 21 Oct 2016 none BSD-3-Clause — Details →
3.0.0-beta 21 Oct 2016 none BSD-3-Clause — Details →
1.6.7 21 Oct 2016 none BSD-3-Clause — Details →
2.4.0 30 Mar 2016 none BSD-3-Clause — Details →
2.3.0 06 Feb 2016 none BSD-3-Clause — Details →
1.6.6 12 Jan 2016 none BSD-3-Clause — Details →
2.2.4 12 Jan 2016 none BSD-3-Clause — Details →
2.2.3 02 Nov 2015 none BSD-3-Clause — Details →
2.2.2 02 Sep 2015 none BSD-3-Clause — Details →
2.2.1 23 Jun 2015 none BSD-3-Clause — Details →
2.2.0 16 Jun 2015 none BSD-3-Clause — Details →
2.1.9 27 Apr 2015 none BSD-3-Clause — Details →
2.1.8 13 Apr 2015 none BSD-3-Clause — Details →
1.6.5 08 Apr 2015 M1 BSD-3-Clause Yes Details →
2.1.7 08 Apr 2015 none BSD-3-Clause — Details →
2.1.6 17 Mar 2015 none BSD-3-Clause — Details →
2.1.5 20 Jan 2015 none BSD-3-Clause — Details →
2.1.4 23 Oct 2014 none BSD-3-Clause — Details →
2.1.3 21 Oct 2014 none BSD-3-Clause — Details →
2.1.2 23 Sep 2014 none BSD-3-Clause — Details →
2.1.1 22 Sep 2014 none BSD-3-Clause — Details →
2.1.0 10 Sep 2014 none BSD-3-Clause — Details →
2.0.1 11 Aug 2014 none BSD-3-Clause — Details →
2.0.0 01 Jul 2014 none BSD-3-Clause — Details →
2.0.0-beta1 20 Jun 2014 none BSD-3-Clause — Details →
2.0.0-beta0 18 Jun 2014 none BSD-3-Clause — Details →
1.6.4 12 Jun 2014 M2 BSD-3-Clause Yes Details →
1.6.3 19 May 2014 M2 BSD-3-Clause Yes Details →
1.6.2 07 Mar 2014 M2 BSD-3-Clause Yes Details →
1.6.2-beta0 25 Feb 2014 M2 BSD-3-Clause Yes Details →
1.0.0-alpha0 22 Jan 2014 M2 BSD-3-Clause Yes Details →
1.0.0-alpha1 22 Jan 2014 M2 BSD-3-Clause Yes Details →
1.0.0-alpha2 22 Jan 2014 M2 BSD-3-Clause Yes Details →
1.6.1 22 Jan 2014 M2 BSD-3-Clause Yes Details →
1.6.0 06 Jan 2014 M2 BSD-3-Clause Yes Details →
1.6.0-beta0 20 Dec 2013 M2 BSD-3-Clause Yes Details →
1.5.2 11 Dec 2013 M2 BSD-3-Clause Yes Details →
1.5.1 03 Dec 2013 M2 BSD-3-Clause Yes Details →
1.5.0 21 Nov 2013 M2 BSD-3-Clause Yes Details →
1.4.2 12 Nov 2013 M2 BSD-3-Clause Yes Details →
1.4.1 11 Nov 2013 M2 BSD-3-Clause Yes Details →
1.4.0 23 Oct 2013 M2 BSD-3-Clause Yes Details →
1.3.1 16 Jul 2013 M2 BSD-3-Clause Yes Details →
1.3.0 15 Jul 2013 M2 BSD-3-Clause Yes Details →
1.2.0 28 Jun 2013 M2 BSD-3-Clause Yes Details →
1.1.0 27 Jun 2013 M2 BSD-3-Clause Yes Details →
1.0.4 14 Jun 2013 M2 BSD-3-Clause Yes Details →
1.0.3 17 May 2013 M2 BSD-3-Clause Yes Details →
1.0.2 30 Apr 2013 M2 BSD-3-Clause Yes Details →
1.0.1 30 Apr 2013 M2 BSD-3-Clause Yes Details →
1.0.0 18 Apr 2013 M2 BSD-3-Clause Yes Details →
0.6.7 11 Dec 2012 M2 BSD-3-Clause Yes Details →
0.6.7-dev 20 Nov 2012 M2 BSD-3-Clause Yes Details →
0.6.6 02 Oct 2012 M2 BSD-3-Clause Yes Details →
0.6.5 29 Aug 2012 M2 BSD-3-Clause Yes Details →
0.6.4-dev 22 Aug 2012 M2 BSD-3-Clause Yes Details →
0.6.4 14 Aug 2012 M2 BSD-3-Clause Yes Details →
0.6.3 08 Aug 2012 M2 BSD-3-Clause Yes Details →
0.6.0-dev 23 Jul 2012 M2 BSD-3-Clause Yes Details →
0.3.0 12 Jul 2012 M2 BSD-3-Clause Yes Details →
0.1.0 09 Jul 2012 M2 BSD-3-Clause Yes Details →

All 68 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 2

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

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-1000043: Content Injection via TileJSON Name in mapbox.js 6.1 medium 1.6.6 09 Nov 2018
CVE-2017-1000042: Content Injection via TileJSON attribute in mapbox.js 6.1 medium 1.6.5 09 Nov 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 mapbox.js

Is mapbox.js safe to use?

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

Vulert scores mapbox.js 65/100, which reads as usable, but worth attention. 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 mapbox.js affected?

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

Which version of mapbox.js should I use?

3.3.1 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 mapbox.js have?

2 vulnerabilities are recorded for mapbox.js 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 mapbox.js vulnerabilities disclosed?

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

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mapbox.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.