VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

auth0-lock: vulnerability history, versions and safety

auth0-lock is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 84 releases, from Jan 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
4 vulnerabilities recorded H1 M2 L1
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 auth0-lock vulnerabilities

Vulert verdict on auth0-lock 15.0.2 i

Updated on 23 Oct 2026

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

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

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

  • Current release 15.0.2 — unaffected i
  • Vulnerabilities on record 4 over 2 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Depended on by 2 packages i
  • Stars 1,141 i
  • OpenSSF scorecard 6/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 auth0-lock, 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
13.2.1 14 Oct 2026 none MIT — Details →
15.0.2 13 Oct 2026 none MIT — Details →
15.0.1 30 Jun 2026 none MIT — Details →
15.0.0 05 Jun 2026 none MIT — Details →
14.3.0 06 Apr 2026 none MIT — Details →
14.2.5 19 Mar 2026 none MIT — Details →
14.2.4 21 Jan 2026 none MIT — Details →
14.2.3 12 Jan 2026 none MIT — Details →
14.2.2 17 Dec 2025 none MIT — Details →
14.2.1 03 Dec 2025 none MIT — Details →
14.2.0 21 Oct 2025 none MIT — Details →
14.1.0 15 Sep 2025 none MIT — Details →
13.2.0 07 Aug 2025 none MIT — Details →
13.1.0 28 Jul 2025 none MIT — Details →
14.0.0 02 Jun 2025 none MIT — Details →
13.0.0 12 Nov 2024 none MIT — Details →
12.5.1 30 May 2024 none MIT — Details →
12.5.0 30 Apr 2024 none MIT — Details →
12.4.0 04 Jan 2024 none MIT — Details →
12.3.1 13 Nov 2023 none MIT — Details →
12.3.0 06 Oct 2023 none MIT — Details →
12.2.0 18 Sep 2023 none MIT — Details →
12.1.0 17 Jul 2023 none MIT — Details →
12.0.2 10 Feb 2023 none MIT — Details →
11.35.1 02 Feb 2023 none MIT — Details →
12.0.1 01 Feb 2023 none MIT — Details →
12.0.0 20 Jan 2023 none MIT — Details →
11.35.0 19 Dec 2022 none MIT — Details →
12.0.0-beta.0 12 Dec 2022 none MIT — Details →
11.34.2 11 Oct 2022 none MIT — Details →
11.34.1 29 Sep 2022 none MIT — Details →
11.34.0 15 Sep 2022 none MIT — Details →
11.33.3 16 Aug 2022 none MIT — Details →
11.33.2 29 Jun 2022 none MIT — Details →
11.33.1 14 Jun 2022 none MIT — Details →
11.33.0 05 May 2022 none MIT — Details →
11.32.2 09 Feb 2022 M1 MIT Yes Details →
11.32.1 27 Jan 2022 M1 MIT Yes Details →
11.32.0 07 Jan 2022 M1 MIT Yes Details →
11.31.1 02 Nov 2021 M1 MIT Yes Details →
11.31.0 15 Oct 2021 M1 MIT Yes Details →
11.30.6 28 Sep 2021 M1 MIT Yes Details →
11.30.5 13 Sep 2021 M1 MIT Yes Details →
11.30.4 12 Jul 2021 M1 MIT Yes Details →
11.30.3 25 Jun 2021 M1 MIT Yes Details →
11.30.2 11 Jun 2021 M1 MIT Yes Details →
11.30.1 04 Jun 2021 M1 MIT Yes Details →
11.30.0 27 Apr 2021 H1 M1 MIT Yes Details →
11.29.1 14 Apr 2021 H1 M1 MIT Yes Details →
11.29.0 06 Apr 2021 H1 M1 MIT Yes Details →
11.28.1 01 Mar 2021 H1 M1 MIT Yes Details →
11.28.0 12 Jan 2021 H1 M1 MIT Yes Details →
11.27.2 17 Dec 2020 H1 M1 MIT Yes Details →
11.27.1 27 Oct 2020 H1 M1 MIT Yes Details →
11.27.0 18 Sep 2020 H1 M1 MIT Yes Details →
11.26.3 14 Aug 2020 H1 M1 MIT Yes Details →
11.26.2 12 Aug 2020 H1 M1 L1 MIT Yes Details →
11.26.1 23 Jul 2020 H1 M1 L1 MIT Yes Details →
11.26.0 23 Jul 2020 H1 M1 L1 MIT Yes Details →
11.25.1 14 Jul 2020 H1 M1 L1 MIT Yes Details →
11.25.0 09 Jul 2020 H1 M1 L1 MIT Yes Details →
11.24.5 03 Jul 2020 H1 M1 L1 MIT Yes Details →
11.24.4 02 Jul 2020 H1 M1 L1 MIT Yes Details →
11.24.3 25 Jun 2020 H1 M1 L1 MIT Yes Details →
11.24.2 05 Jun 2020 H1 M1 L1 MIT Yes Details →
11.24.1 18 May 2020 H1 M1 L1 MIT Yes Details →
11.24.0 11 May 2020 H1 M1 L1 MIT Yes Details →
11.23.1 21 Apr 2020 H1 M1 L1 MIT Yes Details →
11.23.0 02 Apr 2020 H1 M1 L1 MIT Yes Details →
11.22.5 26 Mar 2020 H1 M1 L1 MIT Yes Details →
11.22.4 06 Mar 2020 H1 M1 L1 MIT Yes Details →
11.22.3 04 Mar 2020 H1 M1 L1 MIT Yes Details →
11.22.2 21 Feb 2020 H1 M1 L1 MIT Yes Details →
11.22.1 18 Feb 2020 H1 M1 L1 MIT Yes Details →
11.22.0 17 Feb 2020 H1 M1 L1 MIT Yes Details →
11.21.1 03 Feb 2020 H1 M1 L1 MIT Yes Details →
11.21.0 30 Jan 2020 H1 M1 L1 MIT Yes Details →
11.20.4 29 Jan 2020 H1 M2 L1 MIT Yes Details →
11.20.3 15 Jan 2020 H1 M2 L1 MIT Yes Details →
11.20.2 06 Jan 2020 H1 M2 L1 MIT Yes Details →
11.20.1 20 Dec 2019 H1 M2 L1 MIT Yes Details →
11.20.0 16 Dec 2019 H1 M2 L1 MIT Yes Details →
11.19.0 04 Dec 2019 H1 M2 L1 MIT Yes Details →
11.18.1 28 Oct 2019 H1 M2 L1 MIT Yes Details →
11.18.0 11 Oct 2019 H1 M2 L1 MIT Yes Details →
11.17.3 03 Oct 2019 H1 M2 L1 MIT Yes Details →
11.17.2 08 Aug 2019 H1 M2 L1 MIT Yes Details →
11.17.1 24 Jul 2019 H1 M2 L1 MIT Yes Details →
11.17.0 15 Jul 2019 H1 M2 L1 MIT Yes Details →
11.16.3 11 Jun 2019 H1 M2 L1 MIT Yes Details →
11.16.2 03 Jun 2019 H1 M2 L1 MIT Yes Details →
11.16.1 03 Jun 2019 H1 M2 L1 MIT Yes Details →
11.16.0 06 May 2019 H1 M2 L1 MIT Yes Details →
11.15.0 16 Apr 2019 H1 M2 L1 MIT Yes Details →
11.14.1 20 Mar 2019 H1 M2 L1 MIT Yes Details →
11.14.0 30 Jan 2019 H1 M2 L1 MIT Yes Details →
11.13.2 28 Jan 2019 H1 M2 L1 MIT Yes Details →
11.13.1 23 Jan 2019 H1 M2 L1 MIT Yes Details →
11.13.0 15 Jan 2019 H1 M2 L1 MIT Yes Details →
11.12.1 23 Nov 2018 H1 M2 L1 MIT Yes Details →
11.12.0 20 Nov 2018 H1 M2 L1 — Yes Details →
11.11.0 23 Oct 2018 H1 M2 L1 — Yes Details →
11.10.0 27 Sep 2018 H1 M2 L1 — Yes Details →
11.9.1 11 Sep 2018 H1 M2 L1 — Yes Details →
11.9.0 28 Aug 2018 H1 M2 L1 — Yes Details →
11.8.1 30 Jul 2018 H1 M2 L1 — Yes Details →
11.8.0 24 Jul 2018 H1 M2 L1 — Yes Details →
11.7.2 07 Jun 2018 H1 M2 L1 — Yes Details →
11.7.1 01 Jun 2018 H1 M2 L1 — Yes Details →
11.7.0 28 May 2018 H1 M2 L1 — Yes Details →
11.6.1 02 May 2018 H1 M2 L1 — Yes Details →
11.6.0 25 Apr 2018 H1 M2 L1 — Yes Details →
11.5.2 28 Mar 2018 H1 M2 L1 — Yes Details →
11.5.1 23 Mar 2018 H1 M2 L1 — Yes Details →
11.5.0 22 Mar 2018 H1 M2 L1 — Yes Details →
11.4.0 12 Mar 2018 H1 M2 L1 — Yes Details →
11.3.1 01 Mar 2018 H1 M2 L1 — Yes Details →
11.3.0 23 Feb 2018 H1 M2 L1 — Yes Details →
11.2.3 08 Feb 2018 H1 M2 L1 — Yes Details →
11.2.2 05 Feb 2018 H1 M2 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2021 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for auth0-lock

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-32641: Reflected XSS in auth0-lock 8.1 high 11.30.1 04 Jun 2021
CVE-2020-15119: DOM-based XSS in auth0-lock 6.4 low 11.26.3 19 Aug 2020
CVE-2022-29172: Cross-site Scripting in Auth0 Lock 6.1 medium 11.33.0 24 May 2022
CVE-2019-20174: Vulnerability in auth0-lock Package - Placeholder Property Abuse 6.1 medium 11.21.0 31 Jan 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 auth0-lock

Is auth0-lock safe to use?

Vulert records 4 vulnerabilities for auth0-lock in npm: 0 critical, 1 high, 2 medium and 1 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 auth0-lock's Vulert package health score?

Vulert scores auth0-lock 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 auth0-lock affected?

No. 15.0.2, 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 auth0-lock have?

4 vulnerabilities are recorded for auth0-lock in the npm ecosystem: 0 critical, 1 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new auth0-lock vulnerabilities disclosed?

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

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