VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

ash_authentication: vulnerability history, versions and safety

ash_authentication is a package in the Hex ecosystem. Vulert records 21 vulnerabilities for it across 117 releases, from Feb 2025 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
21 vulnerabilities recorded C1 M2 U18
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
19 in the last 12 months

Most recent disclosure 17 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ash_authentication vulnerabilities

Vulert verdict on ash_authentication 5.0.0-rc.15 i

Updated on 23 Oct 2026

Good news: 5.0.0-rc.15, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 21.

Package health score 64/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

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

  • Current release 5.0.0-rc.15 — unaffected i
  • Vulnerabilities on record 21 over 1 year · 19 in the last year i
  • Latest disclosure 17 Sep 2026 i
  • Highest CVSS 9.2 i
  • With no published fix 0 i
  • Depended on by 1,010,971 packages i
  • Last release this month i

Version list, release dates, licence and dependants published by hex.pm, 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 ash_authentication, 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
5.0.0-rc.15 16 Oct 2026 none — — Details →
5.0.0-rc.14 17 Sep 2026 none — — Details →
5.0.0-rc.13 25 Aug 2026 U14 — Yes Details →
5.0.0-rc.12 08 Jul 2026 U16 — Yes Details →
5.0.0-rc.11 15 Jun 2026 U16 — Yes Details →
5.0.0-rc.10 15 Jun 2026 U16 — Yes Details →
5.0.0-rc.9 11 May 2026 U15 — Yes Details →
5.0.0-rc.8 08 May 2026 U15 — Yes Details →
5.0.0-rc.7 04 May 2026 U15 — Yes Details →
5.0.0-rc.6 04 May 2026 U15 — Yes Details →
5.0.0-rc.5 30 Apr 2026 U15 — Yes Details →
5.0.0-rc.4 30 Apr 2026 U15 — Yes Details →
5.0.0-rc.3 13 Apr 2026 U15 — Yes Details →
5.0.0-rc.2 12 Apr 2026 U15 — Yes Details →
5.0.0-rc.1 09 Feb 2026 U16 — Yes Details →
5.0.0-rc.0 27 Jan 2026 U16 — Yes Details →
4.15.0 17 Sep 2026 none — — Details →
4.14.2 25 Aug 2026 U14 — Yes Details →
4.14.1 15 Jun 2026 U16 — Yes Details →
4.14.0 14 Jun 2026 U16 — Yes Details →
4.13.7 13 Jan 2026 C1 U16 — Yes Details →
4.13.6 04 Jan 2026 C1 U16 — Yes Details →
4.13.5 04 Jan 2026 C1 U16 — Yes Details →
4.13.4 12 Dec 2025 C1 U16 — Yes Details →
4.13.3 01 Dec 2025 C1 U16 — Yes Details →
4.13.2 30 Nov 2025 C1 U16 — Yes Details →
4.13.1 28 Nov 2025 C1 U16 — Yes Details →
4.13.0 17 Nov 2025 C1 U16 — Yes Details →
4.12.0 20 Oct 2025 C1 U16 — Yes Details →
4.11.0 08 Oct 2025 C1 U14 — Yes Details →
4.10.0 11 Sep 2025 C1 U14 — Yes Details →
4.9.9 29 Jul 2025 C1 U13 — Yes Details →
4.9.8 22 Jul 2025 C1 U13 — Yes Details →
4.9.7 17 Jul 2025 C1 U13 — Yes Details →
4.9.6 11 Jul 2025 C1 U13 — Yes Details →
4.9.5 02 Jul 2025 C1 U13 — Yes Details →
4.9.4 19 Jun 2025 C1 U13 — Yes Details →
4.9.3 18 Jun 2025 C1 U13 — Yes Details →
4.9.2 17 Jun 2025 C1 U13 — Yes Details →
4.9.1 16 Jun 2025 C1 U13 — Yes Details →
4.9.0 30 May 2025 C1 U12 — Yes Details →
4.8.7 20 May 2025 C1 U12 — Yes Details →
4.8.6 16 May 2025 C1 U12 — Yes Details →
4.8.5 15 May 2025 C1 U12 — Yes Details →
4.8.3 09 May 2025 C1 U12 — Yes Details →
4.8.2 07 May 2025 C1 U12 — Yes Details →
4.8.1 07 May 2025 C1 U12 — Yes Details →
4.8.0 07 May 2025 C1 U12 — Yes Details →
4.7.6 16 Apr 2025 C1 U10 — Yes Details →
4.7.5 15 Apr 2025 C1 U10 — Yes Details →
4.7.4 15 Apr 2025 C1 U10 — Yes Details →
4.7.3 15 Apr 2025 C1 U10 — Yes Details →
4.7.2 14 Apr 2025 C1 U10 — Yes Details →
4.7.1 14 Apr 2025 C1 U10 — Yes Details →
4.7.0 14 Apr 2025 C1 U10 — Yes Details →
4.6.4 09 Apr 2025 C1 U10 — Yes Details →
4.6.3 27 Mar 2025 C1 U10 — Yes Details →
4.6.2 25 Mar 2025 C1 U10 — Yes Details →
4.6.1 25 Mar 2025 C1 U10 — Yes Details →
4.6.0 20 Mar 2025 C1 U10 — Yes Details →
4.5.6 18 Mar 2025 C1 U10 — Yes Details →
4.5.5 12 Mar 2025 C1 U10 — Yes Details →
4.5.4 12 Mar 2025 C1 U10 — Yes Details →
4.5.3 07 Mar 2025 C1 U10 — Yes Details →
4.5.2 25 Feb 2025 C1 U10 — Yes Details →
4.5.1 14 Feb 2025 C1 U10 — Yes Details →
4.5.0 13 Feb 2025 C1 U10 — Yes Details →
4.4.9 11 Feb 2025 C1 U10 — Yes Details →
4.4.8 04 Feb 2025 C1 U10 — Yes Details →
4.4.7 02 Feb 2025 C1 U10 — Yes Details →
4.4.6 01 Feb 2025 C1 U10 — Yes Details →
4.4.5 28 Jan 2025 C1 U10 — Yes Details →
4.4.4 23 Jan 2025 C1 U10 — Yes Details →
4.4.3 23 Jan 2025 C1 U10 — Yes Details →
4.4.2 22 Jan 2025 C1 U10 — Yes Details →
4.4.1 16 Jan 2025 C1 U10 — Yes Details →
4.4.0 16 Jan 2025 C1 U10 — Yes Details →
4.3.12 14 Jan 2025 C1 U10 — Yes Details →
4.3.11 13 Jan 2025 C1 U10 — Yes Details →
4.3.10 13 Jan 2025 C1 U10 — Yes Details →
4.3.9 31 Dec 2024 C1 U10 — Yes Details →
4.3.8 31 Dec 2024 C1 U10 — Yes Details →
4.3.7 26 Dec 2024 C1 U9 — Yes Details →
4.3.6 20 Dec 2024 C1 U9 — Yes Details →
4.3.5 12 Dec 2024 C1 U9 — Yes Details →
4.3.4 02 Dec 2024 C1 U9 — Yes Details →
4.3.3 14 Nov 2024 C1 U9 — Yes Details →
4.3.2 13 Nov 2024 C1 U9 — Yes Details →
4.3.1 12 Nov 2024 C1 U9 — Yes Details →
4.3.0 05 Nov 2024 C1 U9 — Yes Details →
4.2.7 01 Nov 2024 C1 U9 — Yes Details →
4.2.6 31 Oct 2024 C1 U9 — Yes Details →
4.2.5 23 Oct 2024 C1 U9 — Yes Details →
4.2.4 23 Oct 2024 C1 U9 — Yes Details →
4.2.3 19 Oct 2024 C1 U9 — Yes Details →
4.2.2 15 Oct 2024 C1 U9 — Yes Details →
4.2.1 14 Oct 2024 C1 U9 — Yes Details →
4.2.0 07 Oct 2024 C1 U9 — Yes Details →
4.1.0 06 Oct 2024 C1 U8 — Yes Details →
4.0.4 01 Sep 2024 C1 U8 — Yes Details →
4.0.3 22 Aug 2024 C1 U8 — Yes Details →
4.0.2 05 Aug 2024 C1 U8 — Yes Details →
4.0.1 11 Jun 2024 C1 U8 — Yes Details →
4.0.0 10 May 2024 C1 U8 — Yes Details →
4.0.0-rc.6 11 Apr 2024 C1 U8 — Yes Details →
4.0.0-rc.5 10 Apr 2024 C1 U8 — Yes Details →
4.0.0-rc.3 08 Apr 2024 C1 U8 — Yes Details →
4.0.0-rc.2 02 Apr 2024 C1 U8 — Yes Details →
4.0.0-rc.1 01 Apr 2024 C1 U8 — Yes Details →
4.0.0-rc.0 28 Mar 2024 C1 U8 — Yes Details →
3.12.4 11 Mar 2024 C1 U8 — Yes Details →
3.12.3 20 Feb 2024 C1 U8 — Yes Details →
3.12.2 30 Jan 2024 C1 U8 — Yes Details →
3.12.1 25 Jan 2024 C1 U8 — Yes Details →
3.12.0 21 Nov 2023 C1 U8 — Yes Details →
3.11.16 25 Oct 2023 C1 U8 — Yes Details →
3.11.15 22 Sep 2023 C1 U8 — Yes Details →
3.11.14 22 Sep 2023 C1 U8 — Yes Details →
3.11.13 22 Sep 2023 C1 U8 — Yes Details →
3.11.12 21 Sep 2023 C1 U8 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2
  • 2026 19

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

03 Vulnerabilities

Recorded vulnerabilities for ash_authentication

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2026-49757: AshAuthentication OAuth2/OIDC Account Takeover via Email Matching 9.2 critical 4.14.0 15 Jun 2026
CVE-2026-49757: AshAuthentication OAuth2/OIDC Account Takeover via Email Matching 9.2 critical 4.14.0 25 Aug 2026
CVE-2026-85500: AshAuthentication Authentication Bypass Vulnerability 9.1 critical 4.15.0 17 Sep 2026
CVE-2026-86533: AshAuthentication and AshAuthentication Phoenix Insufficient Session Expiration Vulnerability 9.1 critical 4.15.0 17 Sep 2026
CVE-2026-82761: AshAuthentication Magic Link Token Replay Vulnerability 9.1 critical 4.15.0 17 Sep 2026

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 ash_authentication

Is ash_authentication safe to use?

Vulert records 21 vulnerabilities for ash_authentication in Hex: 1 critical, 0 high, 2 medium and 0 low, plus 18 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ash_authentication's Vulert package health score?

Vulert scores ash_authentication 64/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 ash_authentication affected?

No. 5.0.0-rc.15, 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 ash_authentication have?

21 vulnerabilities are recorded for ash_authentication in the Hex ecosystem: 1 critical, 0 high, 2 medium and 0 low, plus 18 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ash_authentication vulnerabilities disclosed?

19 vulnerabilities were recorded for ash_authentication in the last 12 months, and the oldest entry in this database dates to 11 Feb 2025. 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 ash_authentication 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 ash_authentication for upcoming vulnerabilities?

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