Quick answers
- Is CVE-2026-82727 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82727 being exploited in the wild.
- How severe is CVE-2026-82727?
- Informational severity, with a CVSS score of 0, published 31 August 2026.
- Which products and versions are affected?
- Ash-Project Ash Phoenix 1.2.17 through 2.3.24.
- Is there a fix for CVE-2026-82727?
- 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-82727 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82727?
- 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 is an information disclosure issue in AshPhoenix.Form.Auto's union sub-form handling. When a submitted _union_type parameter does not match a configured type, the error message is constructed using inspect(params, pretty: true), which embeds the full untrusted parameter map and internal union constraints. Because the message is built by the library rather than Phoenix's parameter logger, the standard config :phoenix, :filter_parameters configuration does not redact secrets. An attacker can submit malicious parameters (e.g., %{"_union_type" => "invalid", "password" => "secret123"}) to trigger an exception with the plaintext secret embedded in the message. The fix restricts error messages to report only the invalid _union_type value and valid type names, removing parameter and constraint dumps. Versions 1.2.17 through 2.3.24 are affected; patched in 2.3.25.
Affected products
- ash-project ash_phoenix 1.2.17 through 2.3.24
Timeline
- 2026-08-31: disclosed