VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@firebase/auth: vulnerability history, versions and safety

@firebase/auth is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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 @firebase/auth vulnerabilities

Vulert verdict on @firebase/auth 1.13.8 i

Updated on 23 Oct 2026

Good news: 1.13.8, the version you would install today, has no known vulnerabilities.

Package health score 88/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 1.13.8 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 141 packages i
  • Stars 5,154 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Apache-2.0 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 @firebase/auth, 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
1.13.7-eap-crashlytics.fd9b1e1d0 21 Oct 2026 none Apache-2.0 — Details →
1.13.8 21 Oct 2026 none Apache-2.0 — Details →
1.13.8-20261020134659 20 Oct 2026 none Apache-2.0 — Details →
1.13.7 07 Oct 2026 none Apache-2.0 — Details →
1.13.7-20261007162724 07 Oct 2026 none Apache-2.0 — Details →
1.13.7-20261006213730 06 Oct 2026 none Apache-2.0 — Details →
1.13.7-20261006011744 06 Oct 2026 none Apache-2.0 — Details →
1.13.4-eap-crashlytics.64ada57eb 01 Oct 2026 none Apache-2.0 — Details →
1.13.4-eap-crashlytics.e21972d2a 11 Sep 2026 none Apache-2.0 — Details →
1.13.6-crashlytics2.142b40983 11 Sep 2026 none Apache-2.0 — Details →
1.13.6 09 Sep 2026 none Apache-2.0 — Details →
1.13.6-20260909154321 09 Sep 2026 none Apache-2.0 — Details →
1.13.5 19 Aug 2026 none Apache-2.0 — Details →
1.13.5-20260818172054 18 Aug 2026 none Apache-2.0 — Details →
1.13.4 30 Jul 2026 none Apache-2.0 — Details →
1.13.4-20260728185501 28 Jul 2026 none Apache-2.0 — Details →
1.13.3-eap-crashlytics.659b578fb 21 Jul 2026 none Apache-2.0 — Details →
1.13.3 16 Jun 2026 none Apache-2.0 — Details →
1.13.3-20260616175646 16 Jun 2026 none Apache-2.0 — Details →
1.13.3-20260616165109 16 Jun 2026 none Apache-2.0 — Details →
1.13.3-20260615181107 15 Jun 2026 none Apache-2.0 — Details →
1.13.2-eap-crashlytics.558ee841d 15 Jun 2026 none Apache-2.0 — Details →
1.13.2 28 May 2026 none Apache-2.0 — Details →
1.13.1-eap-crashlytics.06423a1af 27 May 2026 none Apache-2.0 — Details →
1.13.1-eap-crashlytics.3dd4e65d9 26 May 2026 none Apache-2.0 — Details →
1.13.2-20260526192810 26 May 2026 none Apache-2.0 — Details →
1.13.1 07 May 2026 none Apache-2.0 — Details →
1.13.1-20260505185142 05 May 2026 none Apache-2.0 — Details →
1.13.1-20260505164105 05 May 2026 none Apache-2.0 — Details →
1.13.1-20260505131936 05 May 2026 none Apache-2.0 — Details →
1.13.0 09 Apr 2026 none Apache-2.0 — Details →
1.13.0-20260409172004 09 Apr 2026 none Apache-2.0 — Details →
1.13.0-20260408221811 08 Apr 2026 none Apache-2.0 — Details →
1.13.0-20260408201731 08 Apr 2026 none Apache-2.0 — Details →
1.12.2-canary.bfb9accdc 01 Apr 2026 none Apache-2.0 — Details →
1.12.2-canary.742e17a8e 31 Mar 2026 none Apache-2.0 — Details →
1.12.2-canary.44ad4cc2e 25 Mar 2026 none Apache-2.0 — Details →
1.12.2-canary.f4e0086e3 23 Mar 2026 none Apache-2.0 — Details →
1.12.2-canary.ba0bc39bb 20 Mar 2026 none Apache-2.0 — Details →
1.12.2 19 Mar 2026 none Apache-2.0 — Details →
1.12.2-20260317152345 17 Mar 2026 none Apache-2.0 — Details →
1.12.1-canary.843a8d789 17 Mar 2026 none Apache-2.0 — Details →
1.12.1-canary.891a0c9d4 17 Mar 2026 none Apache-2.0 — Details →
1.12.1-canary.d7b182645 11 Mar 2026 none Apache-2.0 — Details →
1.12.1-canary.792c61671 05 Mar 2026 none Apache-2.0 — Details →
1.12.1-canary.22476e1bc 02 Mar 2026 none Apache-2.0 — Details →
1.12.1-canary.78384d32c 02 Mar 2026 none Apache-2.0 — Details →
1.12.1 27 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.920624ade 26 Feb 2026 none Apache-2.0 — Details →
1.12.1-20260224183151 24 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.46fa57f9e 19 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.f0b0398eb 19 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.47f85219d 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.7b1e6ec79 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.d4b22a872 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.4d2ab8507 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.c48b47674 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.9ced4281d 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.d7c311a4b 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.93eeffcb3 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.35b284af4 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.2bd48a604 18 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.e4b2890fd 05 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.b10a296fa 03 Feb 2026 none Apache-2.0 — Details →
1.12.0-canary.f9254b6d2 30 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.8123231a1 29 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.691a506ec 29 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.65a553baf 29 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.2e7432986 29 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.c4a3a5643 27 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.f9aaeca46 26 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.08e3acdf0 26 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.d818df4e8 21 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.58ddd6e54 16 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.817151ee9 15 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.efc0117ae 14 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.d5ff5a4b1 14 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.b2827448b 13 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.5579b387a 12 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.8bac8f0b2 07 Jan 2026 none Apache-2.0 — Details →
1.12.0-canary.9cf4b7e35 05 Jan 2026 none Apache-2.0 — Details →
1.11.0-caching-fdc.9f17eac6e 16 Dec 2025 none Apache-2.0 — Details →
1.12.0-canary.8e26a5590 16 Dec 2025 none Apache-2.0 — Details →
1.12.0 16 Dec 2025 none Apache-2.0 — Details →
1.12.0-20251215180848 15 Dec 2025 none Apache-2.0 — Details →
1.11.1-canary.bc2b2cdea 12 Dec 2025 none Apache-2.0 — Details →
1.11.1-canary.5511b4fa7 09 Dec 2025 none Apache-2.0 — Details →
1.11.1-canary.1e406a2b7 04 Dec 2025 none Apache-2.0 — Details →
1.11.1-canary.a09ef786f 04 Dec 2025 none Apache-2.0 — Details →
1.11.1-canary.5c7430dea 03 Dec 2025 none Apache-2.0 — Details →
1.11.1-canary.f5fc6bf76 01 Dec 2025 none Apache-2.0 — Details →
1.11.1-canary.9101b4611 01 Dec 2025 none Apache-2.0 — Details →
1.11.1-canary.e6415ddee 25 Nov 2025 none Apache-2.0 — Details →
1.11.1-canary.59407948d 24 Nov 2025 none Apache-2.0 — Details →
1.11.1-canary.60d1b18bd 20 Nov 2025 none Apache-2.0 — Details →
1.11.1-canary.d1d898f55 14 Nov 2025 none Apache-2.0 — Details →
1.11.1-canary.578686b0b 13 Nov 2025 none Apache-2.0 — Details →
1.11.1-canary.b228a2ab9 13 Nov 2025 none Apache-2.0 — Details →
1.11.1-canary.180b1ad9b 13 Nov 2025 none Apache-2.0 — Details →
1.11.1-canary.5c35f514c 12 Nov 2025 none Apache-2.0 — Details →
1.11.1-canary.f06cbf99b 12 Nov 2025 none — — Details →
1.11.1-canary.6abe52967 11 Nov 2025 none — — Details →
1.11.1-eap-firestore-pipelines.2.e4cdd2e06 06 Nov 2025 none — — Details →
1.11.1-canary.0800a8bed 05 Nov 2025 none — — Details →
1.11.1-eap-firestore-pipelines.1.f9c4cdec7 05 Nov 2025 none — — Details →
1.11.1-canary.c47bd7175 30 Oct 2025 none — — Details →
1.11.1-canary.63167c68a 30 Oct 2025 none — — Details →
1.11.1 30 Oct 2025 none — — Details →
1.11.0-canary.6e0e30317 28 Oct 2025 none — — Details →
1.11.1-20251028194003 28 Oct 2025 none — — Details →
1.11.0-canary.bc5a7c4a7 28 Oct 2025 none — — Details →
1.11.0-canary.8209266c6 21 Oct 2025 none — — Details →
1.11.0-canary.22e0a1adb 20 Oct 2025 none — — Details →
1.11.0-canary.91c218db2 20 Oct 2025 none — — Details →
1.11.0-canary.44d9891f9 20 Oct 2025 none — — Details →
1.11.0-canary.c8263c471 16 Oct 2025 none — — Details →
1.11.0-canary.261508183 10 Oct 2025 none — — Details →
1.11.0-canary.b7e18d0ff 09 Oct 2025 none — — Details →
1.11.0-canary.2596dd1b5 07 Oct 2025 none — — Details →
1.11.0-canary.ccbf7ba36 29 Sep 2025 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for @firebase/auth

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 @firebase/auth

Is @firebase/auth safe to use?

Vulert has no vulnerabilities on record for @firebase/auth in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is @firebase/auth's Vulert package health score?

Vulert scores @firebase/auth 88/100, which reads as healthy. 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 @firebase/auth affected?

No. 1.13.8, 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 @firebase/auth have?

0 vulnerabilities are recorded for @firebase/auth in the npm ecosystem: 0 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 @firebase/auth vulnerabilities disclosed?

0 vulnerabilities were recorded for @firebase/auth in the last 12 months. 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 @firebase/auth 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 @firebase/auth for upcoming vulnerabilities?

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