{"answers":{"affected":"1 open source package ship an affected version, including ash_phoenix.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82727 exists.","fix":"Upgrade ash_phoenix to 2.3.25 or later.","what":"CVE-2026-82727 is a low-severity 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."},"fix_prompt":"Check this codebase for CVE-2026-82727 and fix it if it is affected.\n\nWhat it is: CVE-2026-82727 is a low-severity 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82727 exists.\n\nAffected packages and fixed versions:\n- ash_phoenix (Hex): affected from 1.2.17; fixed in 2.3.25\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-82727/ (Markdown: https://insights.sbomify.com/CVE-2026-82727/index.md)","id":"CVE-2026-82727","markdown":"https://insights.sbomify.com/CVE-2026-82727/index.md","name":"CVE-2026-82727","record":{"aliases":["EEF-CVE-2026-82727","GHSA-5xf4-hgcq-xw7v"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir Phoenix library","requires_auth":"low_privilege","summary":"Attackers can leak sensitive submitted parameters, such as passwords, into error logs and crash reports by triggering a union type mismatch in AshPhoenix Form.Auto.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"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.\n\nWhen 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\" =\u003e \"nope\", \"password\" =\u003e \"...\"} 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.\n\nThis issue affects ash_phoenix: from 1.2.17 before 2.3.25.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"AshPhoenix Form.Auto leaks submitted params in an unknown _union_type error message","id":"CVE-2026-82727","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Unbounded HTTP/1 status-line and chunk-extension buffering in Mint causes memory-exhaustion DoS","id":"CVE-2026-82728"},"packages":[{"ecosystem":"Hex","fixed":["2.3.25"],"introduced":["1.2.17"],"last_affected":[],"package":"ash_phoenix","purl":"pkg:hex/ash_phoenix","source":"EEF-CVE-2026-82727"}],"prev":{"headline":"AshPhoenix get_subdomain maps a crafted or differently-cased Host header to an arbitrary tenant","id":"CVE-2026-82726"},"products":["ash_phoenix"],"published":"2026-08-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["ash-project"]},"summary":"Attackers can leak sensitive submitted parameters, such as passwords, into error logs and crash reports by triggering a union type mismatch in AshPhoenix Form.Auto.","url":"https://insights.sbomify.com/CVE-2026-82727/"}