AshPhoenix Form.Auto leaks submitted params in an unknown _union_type error message
ash-project ash_phoenix
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ash-project ash_phoenix |
| No fix yet |
| ash-project ash_phoenix |
| No fix yet |
Original description
Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_phoenix writes the entire raw submitted param map into an exception message, so secrets submitted alongside a union form field leak into logs, crash reports and the dev error page.
When AshPhoenix.Form.Auto builds a union sub-form and the submitted _union_type does not match a configured type, both raise sites built the message with inspect(params, pretty: true), embedding the full untrusted param map, and also inspected the internal union constraints[:types]. Because the message is constructed by the library rather than Phoenix's parameter logger, config :phoenix, :filter_parameters never redacts it. An attacker controls both the trigger and the contents: submitting %{"_union_type" => "nope", "password" => "..."} puts the password verbatim in the raised message. The fix reports only the offending _union_type and the valid type names, dropping the param and constraints dumps.
This issue affects ash_phoenix: from 1.2.17 before 2.3.25.
From the CVE record · EEF
References
- github.com/ash-project/ash_phoenix/security/advisories/GHSA-5xf4-hgcq-xw7vExploit
- cna.erlef.org/cves/CVE-2026-82727.html
- osv.dev/vulnerability/EEF-CVE-2026-82727
- github.com/ash-project/ash_phoenix/commit/a3436fcc321e3b34c242cceaf62c3c92bc1a452b
- github.com/ash-project/ash_phoenix/commit/0c1775c3cf8988f9abd10a8f92315afc5f06f16dPatch
- github.com
- repo.hex.pm
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/82xxx/CVE-2026-82727.json
- nvd.nist.gov/vuln/detail/CVE-2026-82727
- github.com/ash-project/ash_phoenix