AshPhoenix FilterForm allows filtering across non-public relationships, disclosing private related data (CVE-2026-82725) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-82725

AshPhoenix FilterForm allows filtering across non-public relationships, disclosing private related data

Answer in brief

CVE-2026-82725 records a Unknown severity vulnerability in AshPhoenix FilterForm allows filtering across non-public relationships, disclosing private related data. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_phoenix (generic), ash-project/ash_phoenix (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 31, 2026Updated Aug 31, 2026Source checked Aug 31, 2026First seen by HOL Aug 31, 2026Material review Aug 31, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps ash-project/ash_phoenix (generic), ash-project/ash_phoenix (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ash-project/ash_phoenixgeneric	>=0.6.0-rc.1 <2.3.25	2.3.25
ash-project/ash_phoenixgeneric	>=06875682999938f607c970e71b6a80af90e18b3d <a3691a3cb0947e8f2dc2c3cbff138a3e6197a15b	a3691a3cb0947e8f2dc2c3cbff138a3e6197a15b

Recommended response

Check inventory. Check lockfiles and deployed manifests for ash-project/ash_phoenix, ash-project/ash_phoenix.
Review the reported fix. Update ash-project/ash_phoenix to 2.3.25; ash-project/ash_phoenix to a3691a3cb0947e8f2dc2c3cbff138a3e6197a15b if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 31, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 31, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 31, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.