Skip to content
Threat Brief

← All advisories

CVE-2026-82727

Low 2.3No known exploitationFix available

AshPhoenix Form.Auto leaks submitted params in an unknown _union_type error message

Record last updated

CVSS score

2.3

Low on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.3%

Higher than 28% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-209

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
ash-projectash_phoenixfrom 1.2.17 before 2.3.252.3.25CVE Program
ash-projectash_phoenixfrom a3436fcc321e3b34c242cceaf62c3c92bc1a452b before 0c1775c3cf8988f9abd10a8f92315afc5f06f16d0c1775c3cf8988f9abd10a8f92315afc5f06f16dCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references