VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

Auth0.AuthenticationApi: vulnerability history, versions and safety

Auth0.AuthenticationApi is a package in the NuGet ecosystem. Vulert records 1 vulnerability for it across 13 releases, first recorded in Oct 2019. 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 H1
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.AuthenticationApi vulnerabilities

Vulert verdict on Auth0.AuthenticationApi 7.49.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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

  • Current release 7.49.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 Oct 2019 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 364 i
  • Last release 2 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by NuGet, 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.AuthenticationApi, 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
7.49.0 19 Aug 2026 none MIT — Details →
7.48.0 23 Jul 2026 none MIT — Details →
7.47.0 29 Jun 2026 none MIT — Details →
7.46.0 13 May 2026 none MIT — Details →
7.45.1 26 Mar 2026 none MIT — Details →
7.45.0 25 Feb 2026 none MIT — Details →
7.44.0 29 Jan 2026 none MIT — Details →
7.43.1 15 Jan 2026 none MIT — Details →
7.43.0 05 Dec 2025 none MIT — Details →
7.42.0 09 Oct 2025 none MIT — Details →
7.41.0 15 Sep 2025 none MIT — Details →
7.40.0 13 Aug 2025 none MIT — Details →
7.39.0 08 Jul 2025 none MIT — Details →
7.38.0 23 Jun 2025 none MIT — Details →
7.37.0 30 May 2025 none MIT — Details →
7.36.0 10 Apr 2025 none MIT — Details →
7.35.0 24 Mar 2025 none MIT — Details →
7.34.0 19 Feb 2025 none MIT — Details →
7.33.0 05 Feb 2025 none MIT — Details →
7.32.0 22 Jan 2025 none MIT — Details →
7.31.0 08 Jan 2025 none MIT — Details →
7.30.0 28 Nov 2024 none MIT — Details →
7.29.0 11 Nov 2024 none MIT — Details →
7.28.0 25 Oct 2024 none MIT — Details →
7.27.0 30 Sep 2024 none MIT — Details →
7.26.2 24 Apr 2024 none MIT — Details →
7.26.1 11 Jan 2024 none MIT — Details →
7.26.0 21 Dec 2023 none MIT — Details →
7.25.1 14 Dec 2023 none MIT — Details →
7.25.0 04 Dec 2023 none MIT — Details →
7.24.0 08 Nov 2023 none MIT — Details →
7.23.1 25 Oct 2023 none MIT — Details →
7.23.0 19 Oct 2023 none MIT — Details →
7.22.3 29 Aug 2023 none MIT — Details →
7.22.2 14 Aug 2023 none MIT — Details →
7.22.1 28 Jul 2023 none MIT — Details →
7.22.0 19 Jul 2023 none MIT — Details →
7.21.1 13 Jul 2023 none MIT — Details →
7.21.0 21 Jun 2023 none MIT — Details →
7.20.0 20 May 2023 none MIT — Details →
7.19.1 08 May 2023 none MIT — Details →
7.19.0 13 Mar 2023 none MIT — Details →
7.18.0 24 Jan 2023 none MIT — Details →
7.17.4 17 Oct 2022 none MIT — Details →
7.17.3 03 Oct 2022 none MIT — Details →
7.17.2 13 Sep 2022 none MIT — Details →
7.17.1 07 Sep 2022 none MIT — Details →
7.17.0 26 Jul 2022 none MIT — Details →
7.16.1 12 Jul 2022 none MIT — Details →
7.16.0 03 May 2022 none MIT — Details →
7.15.0 06 Mar 2022 none MIT — Details →
7.14.0 15 Feb 2022 none MIT — Details →
7.13.0 14 Feb 2022 none MIT — Details →
7.12.1 10 Jan 2022 none MIT — Details →
7.12.0 27 Oct 2021 none MIT — Details →
7.11.0 12 Oct 2021 none MIT — Details →
7.10.0 31 Aug 2021 none MIT — Details →
7.9.0 24 Aug 2021 none MIT — Details →
7.8.1 07 Jul 2021 none MIT — Details →
7.8.0 02 Apr 2021 none MIT — Details →
7.7.0 23 Mar 2021 none MIT — Details →
7.6.1 12 Mar 2021 none MIT — Details →
7.6.0 15 Feb 2021 none MIT — Details →
7.5.1 02 Feb 2021 none MIT — Details →
7.5.0 21 Jan 2021 none MIT — Details →
7.4.0 11 Dec 2020 none MIT — Details →
7.3.2 13 Nov 2020 none MIT — Details →
7.3.1 12 Nov 2020 none MIT — Details →
7.3.0 23 Oct 2020 none MIT — Details →
7.2.0 09 Oct 2020 none MIT — Details →
7.1.0 02 Sep 2020 none MIT — Details →
7.0.9 24 Jun 2020 none MIT — Details →
7.0.8 11 May 2020 none MIT — Details →
7.0.7 24 Apr 2020 none MIT — Details →
7.0.6 23 Apr 2020 none MIT — Details →
7.0.5 20 Apr 2020 none MIT — Details →
7.0.4 01 Apr 2020 none MIT — Details →
7.0.3 30 Mar 2020 none MIT — Details →
7.0.2 09 Mar 2020 none MIT — Details →
7.0.1 12 Feb 2020 none MIT — Details →
7.0.0 30 Jan 2020 none MIT — Details →
7.0.0-beta2 16 Jan 2020 none MIT — Details →
6.5.6 13 Jan 2020 none MIT — Details →
7.0.0-beta1 10 Dec 2019 none MIT — Details →
6.5.5 06 Dec 2019 none MIT — Details →
6.5.4 04 Oct 2019 none MIT — Details →
6.5.3 03 Sep 2019 H1 MIT Yes Details →
6.5.2 27 Aug 2019 H1 MIT Yes Details →
6.5.1 22 Aug 2019 H1 MIT Yes Details →
6.5.0 19 Aug 2019 H1 MIT Yes Details →
6.4.0 23 Jul 2019 H1 MIT Yes Details →
6.3.0 14 Jun 2019 H1 MIT Yes Details →
6.2.0 23 May 2019 H1 MIT Yes Details →
6.1.0 08 May 2019 H1 MIT Yes Details →
6.0.0 02 Apr 2019 H1 MIT Yes Details →
5.11.0 23 Jan 2019 H1 non-standard Yes Details →
5.10.0 30 Aug 2018 H1 non-standard Yes Details →
5.9.0 01 Aug 2018 H1 non-standard Yes Details →
5.8.0 26 Jul 2018 H1 non-standard Yes Details →
5.7.0 09 Jul 2018 none non-standard — Details →
5.6.0 18 Jun 2018 none — — Details →
5.5.0 04 Jun 2018 none — — Details →
5.4.0 28 May 2018 none — — Details →
5.3.1 07 May 2018 none — — Details →
5.3.0 24 Apr 2018 none — — Details →
5.2.0 18 Apr 2018 none — — Details →
5.1.0 30 Mar 2018 none — — Details →
5.0.0 28 Mar 2018 none — — Details →
5.0.0-beta1 23 Mar 2018 none — — Details →
4.3.1 10 Jan 2018 none — — Details →
4.3.0 08 Jan 2018 none — — Details →
4.2.0 12 Jun 2017 none — — Details →
4.1.0 26 Apr 2017 none — — Details →
4.0.0 24 Apr 2017 none — — Details →
4.0.0-beta1 13 Jan 2017 none — — Details →
3.7.0 09 Jan 2017 none — — Details →
3.6.0 28 Nov 2016 none — — Details →
3.5.0 21 Oct 2016 none — — Details →
3.4.1 04 Oct 2016 none — — Details →
3.4.0 27 Sep 2016 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 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 Auth0.AuthenticationApi

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-16929: Improper Authentication in Auth0.AuthenticationApi 7.5 high 6.5.4 24 Oct 2019

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.AuthenticationApi

Is Auth0.AuthenticationApi safe to use?

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

Vulert scores Auth0.AuthenticationApi 82/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.AuthenticationApi affected?

No. 7.49.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 Auth0.AuthenticationApi should I use?

7.49.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 Auth0.AuthenticationApi have?

1 vulnerability is recorded for Auth0.AuthenticationApi in the NuGet ecosystem: 0 critical, 1 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 Auth0.AuthenticationApi vulnerabilities disclosed?

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

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