# CVE-2026-82725: AshPhoenix FilterForm allows filtering across non-public relationships, disclosing private related data

> Attackers can filter across private relationships to disclose sensitive data via boolean oracle attacks in AshPhoenix FilterForm.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** EEF-CVE-2026-82725, GHSA-7xhg-xphm-f458

## What is CVE-2026-82725?

CVE-2026-82725 is a low-severity missing authorization vulnerability in ash-project ash_phoenix, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash_phoenix lets an attacker who controls filter form parameters filter across relationships the resource author marked non-public, turning the returned rows into a boolean oracle over private related data.

AshPhoenix.FilterForm resolved every relationship hop in the user-supplied path with Ash.Resource.Info.related/2, which traverses private relationships, and only checked the terminal field for publicity. parse_path_and_field/2 also rewrote a field naming a relationship into an extra path segment, so field=some_private_rel was accepted too. Both path and field come straight from form params, and the resulting ref went to Ash.Query.do_filter/2 without the public-only enforcement of Ash.Filter.parse_input/2. The fix resolves each hop with Ash.Resource.Info.public_relationship/2, rejecting the first non-public hop, and requires the terminal field to be public.

This issue affects ash_phoenix: from 0.6.0-rc.1 before 2.3.25.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-82725?

1 open source package ship an affected version, including ash_phoenix.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ash_phoenix` | Hex | From 0.6.0-rc.1 | 2.3.25 |

## How do I fix CVE-2026-82725?

Upgrade ash_phoenix to 2.3.25 or later.

## Is CVE-2026-82725 being exploited?

There is no known exploitation of CVE-2026-82725 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82725 and fix it if it is affected.

What it is: CVE-2026-82725 is a low-severity missing authorization vulnerability in ash-project ash_phoenix, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82725 in the wild and no public exploit code.

Affected packages and fixed versions:
- ash_phoenix (Hex): affected from 0.6.0-rc.1; fixed in 2.3.25

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82725/ (Markdown: https://insights.sbomify.com/CVE-2026-82725/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82725
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82725
- OSV: https://osv.dev/vulnerability/CVE-2026-82725

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82725/
Summaries are generated and may contain mistakes; the official description above is the record.