VulertSecurity VulertSecurity

Vulnerability Database · Hex · Package report

ash_phoenix: vulnerability history, versions and safety

ash_phoenix is a package in the Hex ecosystem. Vulert records 4 vulnerabilities for it across 119 releases, first recorded in Aug 2026. 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 U4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 31 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ash_phoenix vulnerabilities

Vulert verdict on ash_phoenix 2.3.25 i

Updated on 22 Oct 2026

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

Package health score 85/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

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

  • Current release 2.3.25 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 31 Aug 2026 i
  • Highest CVSS 7.6 i
  • With no published fix 0 i
  • Depended on by 1,367,543 packages i
  • Last release 1 month ago 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_phoenix, 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
2.3.25 31 Aug 2026 none — — Details →
2.3.24 08 Jul 2026 U4 — Yes Details →
2.3.23 05 Jun 2026 U4 — Yes Details →
2.3.22 02 May 2026 U4 — Yes Details →
2.3.21 13 Apr 2026 U4 — Yes Details →
2.3.20 02 Mar 2026 U4 — Yes Details →
2.3.19 19 Jan 2026 U4 — Yes Details →
2.3.18 05 Nov 2025 U4 — Yes Details →
2.3.17 16 Oct 2025 U4 — Yes Details →
2.3.16 01 Sep 2025 U4 — Yes Details →
2.3.15 31 Aug 2025 U4 — Yes Details →
2.3.14 21 Aug 2025 U4 — Yes Details →
2.3.13 07 Aug 2025 U4 — Yes Details →
2.3.12 29 Jul 2025 U4 — Yes Details →
2.3.11 17 Jul 2025 U4 — Yes Details →
2.3.10 09 Jul 2025 U4 — Yes Details →
2.3.9 28 Jun 2025 U4 — Yes Details →
2.3.8 25 Jun 2025 U4 — Yes Details →
2.3.7 18 Jun 2025 U4 — Yes Details →
2.3.6 10 Jun 2025 U4 — Yes Details →
2.3.5 31 May 2025 U4 — Yes Details →
2.3.4 30 May 2025 U4 — Yes Details →
2.3.3 30 May 2025 U4 — Yes Details →
2.3.2 21 May 2025 U4 — Yes Details →
2.3.1 15 May 2025 U4 — Yes Details →
2.3.0 29 Apr 2025 U4 — Yes Details →
2.2.0 13 Apr 2025 U4 — Yes Details →
2.1.26 09 Apr 2025 U4 — Yes Details →
2.1.25 27 Mar 2025 U2 — Yes Details →
2.1.24 25 Mar 2025 U2 — Yes Details →
2.1.23 21 Mar 2025 U2 — Yes Details →
2.1.22 21 Mar 2025 U2 — Yes Details →
2.1.21 18 Mar 2025 U2 — Yes Details →
2.1.20 11 Mar 2025 U2 — Yes Details →
2.1.19 04 Mar 2025 U2 — Yes Details →
2.1.18 10 Feb 2025 U2 — Yes Details →
2.1.17 30 Jan 2025 U2 — Yes Details →
2.1.16 29 Jan 2025 U2 — Yes Details →
2.1.15 27 Jan 2025 U2 — Yes Details →
2.1.14 19 Jan 2025 U2 — Yes Details →
2.1.13 03 Jan 2025 U2 — Yes Details →
2.1.12 22 Dec 2024 U2 — Yes Details →
2.1.11 20 Dec 2024 U2 — Yes Details →
2.1.10 12 Dec 2024 U2 — Yes Details →
2.1.9 11 Dec 2024 U2 — Yes Details →
2.1.8 29 Oct 2024 U2 — Yes Details →
2.1.7 29 Oct 2024 U2 — Yes Details →
2.1.6 17 Oct 2024 U2 — Yes Details →
2.1.5 14 Oct 2024 U2 — Yes Details →
2.1.4 30 Sep 2024 U2 — Yes Details →
2.1.3 30 Sep 2024 U2 — Yes Details →
2.1.2 03 Sep 2024 U2 — Yes Details →
2.1.1 01 Aug 2024 U2 — Yes Details →
2.1.0 26 Jul 2024 U2 — Yes Details →
2.0.4 13 Jun 2024 U2 — Yes Details →
2.0.3 05 Jun 2024 U2 — Yes Details →
2.0.2 22 May 2024 U2 — Yes Details →
2.0.1 17 May 2024 U2 — Yes Details →
2.0.0 10 May 2024 U2 — Yes Details →
2.0.0-rc.8 30 Apr 2024 U2 — Yes Details →
2.0.0-rc.7 23 Apr 2024 U2 — Yes Details →
2.0.0-rc.6 19 Apr 2024 U2 — Yes Details →
2.0.0-rc.5 16 Apr 2024 U2 — Yes Details →
2.0.0-rc.4 05 Apr 2024 U2 — Yes Details →
2.0.0-rc.3 04 Apr 2024 U2 — Yes Details →
2.0.0-rc.2 02 Apr 2024 U2 — Yes Details →
2.0.0-rc.1 28 Mar 2024 U2 — Yes Details →
2.0.0-rc.0 28 Mar 2024 U2 — Yes Details →
1.3.7 28 Jun 2024 U2 — Yes Details →
1.3.6 23 Apr 2024 U2 — Yes Details →
1.3.5 22 Apr 2024 U2 — Yes Details →
1.3.4 11 Mar 2024 U2 — Yes Details →
1.3.3 11 Mar 2024 U2 — Yes Details →
1.3.2 06 Mar 2024 U2 — Yes Details →
1.3.1 04 Feb 2024 U2 — Yes Details →
1.3.0 21 Jan 2024 U2 — Yes Details →
1.2.26 12 Jan 2024 U2 — Yes Details →
1.2.25 02 Jan 2024 U2 — Yes Details →
1.2.24 12 Dec 2023 U2 — Yes Details →
1.2.23 24 Oct 2023 U2 — Yes Details →
1.2.22 24 Oct 2023 U2 — Yes Details →
1.2.21 24 Oct 2023 U2 — Yes Details →
1.2.20 13 Oct 2023 U2 — Yes Details →
1.2.19 27 Sep 2023 U2 — Yes Details →
1.2.18 25 Sep 2023 U2 — Yes Details →
1.2.17 04 Sep 2023 U2 — Yes Details →
1.2.16 26 Jul 2023 U1 — Yes Details →
1.2.15 12 Jul 2023 U1 — Yes Details →
1.2.14 25 May 2023 U1 — Yes Details →
1.2.13 26 Apr 2023 U1 — Yes Details →
1.2.12 03 Apr 2023 U1 — Yes Details →
1.2.11 23 Mar 2023 U1 — Yes Details →
1.2.10 14 Mar 2023 U1 — Yes Details →
1.2.9 09 Mar 2023 U1 — Yes Details →
1.2.8 06 Mar 2023 U1 — Yes Details →
1.2.7 01 Mar 2023 U1 — Yes Details →
1.2.6 15 Feb 2023 U1 — Yes Details →
1.2.5 28 Jan 2023 U1 — Yes Details →
1.2.4 18 Jan 2023 U1 — Yes Details →
1.2.3 21 Dec 2022 U1 — Yes Details →
1.2.2 15 Dec 2022 U1 — Yes Details →
1.2.1 05 Dec 2022 U1 — Yes Details →
1.2.0 30 Nov 2022 U1 — Yes Details →
1.1.2 31 Oct 2022 U1 — Yes Details →
1.1.1 28 Oct 2022 U1 — Yes Details →
1.1.0 17 Oct 2022 U1 — Yes Details →
1.1.0-rc.3 10 Oct 2022 U1 — Yes Details →
1.1.0-rc.2 07 Oct 2022 U1 — Yes Details →
1.1.0-rc.1 28 Sep 2022 U1 — Yes Details →
1.1.0-rc.0 27 Sep 2022 U1 — Yes Details →
1.0.0-rc.1 21 Sep 2022 U1 — Yes Details →
1.0.0-rc.0 30 Aug 2022 U1 — Yes Details →
1.0.0-pre.2 24 Aug 2022 U1 — Yes Details →
1.0.0-pre.1 23 Aug 2022 U1 — Yes Details →
1.0.0-pre.0 23 Aug 2022 U1 — Yes Details →
0.7.7 22 Aug 2022 U1 — Yes Details →
0.7.6-rc.0 15 Aug 2022 U1 — Yes Details →
0.7.5 13 Aug 2022 U1 — Yes Details →
0.7.4 10 Aug 2022 U1 — Yes Details →
0.7.3 10 Aug 2022 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for ash_phoenix

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2026-82724: AshPhoenix SubdomainHook Access Control Vulnerability 7.6 high 2.3.25 31 Aug 2026
CVE-2026-82726: AshPhoenix Package Vulnerability Allows Arbitrary Tenant Selection via Host Header 6.3 medium 2.3.25 31 Aug 2026
CVE-2026-82725: AshPhoenix FilterForm Vulnerability Allows Unauthorized Data Access 2.3 low 2.3.25 31 Aug 2026
CVE-2026-82727: AshPhoenix Form.Auto Sensitive Data Leakage in Error Messages 2.3 low 2.3.25 31 Aug 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: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About ash_phoenix

Is ash_phoenix safe to use?

Vulert records 4 vulnerabilities for ash_phoenix in Hex: 0 critical, 0 high, 0 medium and 0 low, plus 4 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_phoenix's Vulert package health score?

Vulert scores ash_phoenix 85/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 ash_phoenix affected?

No. 2.3.25, 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_phoenix have?

4 vulnerabilities are recorded for ash_phoenix in the Hex ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 4 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_phoenix vulnerabilities disclosed?

4 vulnerabilities were recorded for ash_phoenix in the last 12 months, and the oldest entry in this database dates to 31 Aug 2026. 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_phoenix 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_phoenix for upcoming vulnerabilities?

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