# CVE-2026-82725: ash-project ash_phoenix authorization bypass through user-controlled key

Source: https://junglewise.ai/threats/cve-2026-82725-ash-project-ash-phoenix-authorization-bypass-through-user  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-31. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-82725 · Severity: info · Published 2026-08-31

AshPhoenix is a web framework library used to build data-driven web applications in Elixir. A vulnerability in its filter form processing allows attackers to bypass authorization checks and access private related data by crafting malicious filter parameters, essentially turning the application into an oracle that leaks sensitive information about relationships the application intended to keep hidden.

Technologies: [Ash-Project Ash Phoenix](https://junglewise.ai/threats/technologies/ash-phoenix). Vendors: [Ash-Project](https://junglewise.ai/threats/vendors/ash-project).

## Quick answers

**Is CVE-2026-82725 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-82725 being exploited in the wild.

**How severe is CVE-2026-82725?** Informational severity, published 31 August 2026.

**Which products and versions are affected?** Ash-Project Ash Phoenix 0.6.0-rc.1 before 2.3.25.

**Is there a fix for CVE-2026-82725?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-82725 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-82725?** Check whether you run Ash-Project Ash Phoenix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in AshPhoenix.FilterForm's path parsing logic, which failed to enforce authorization when filtering across relationships. The parse_path_and_field/2 function resolved every relationship hop using Ash.Resource.Info.related/2 (which traverses private relationships) and only checked the terminal field for publicity, rather than validating each hop. Additionally, field parameters naming private relationships were rewritten into extra path segments, bypassing checks. Since path and field parameters come directly from form input without the public-only enforcement of Ash.Filter.parse_input/2, attackers could construct filters that leak boolean information about private related data. The fix enforces public_relationship/2 at each hop and requires the terminal field to be public.

## Affected products

- ash-project ash_phoenix 0.6.0-rc.1 before 2.3.25

## Timeline

- 2026-08-31: disclosed

## References

- [https://repo.hex.pm/](https://repo.hex.pm/)
- [https://github.com/](https://github.com/)

## Related threats

- [ash-project ash_phoenix sensitive information in error messages](https://junglewise.ai/threats/cve-2026-82727-ash-project-ash-phoenix-sensitive-information-in-error-messages)
- [ash-project ash_phoenix regular expression tenant isolation bypass](https://junglewise.ai/threats/cve-2026-82726-ash-project-ash-phoenix-regular-expression-tenant-isolation)
- [ash-project ash_phoenix authorization bypass in SubdomainHook](https://junglewise.ai/threats/cve-2026-82724-ash-project-ash-phoenix-authorization-bypass-in-subdomainhook)