{"answers":{"affected":"1 open source package ship an affected version, including ash_authentication.","exploited":"There is no known exploitation of CVE-2026-86522 in the wild and no public exploit code.","fix":"Upgrade ash_authentication to a fixed version for your release line: 4.15.0 or 5.0.0-rc.14.","what":"CVE-2026-86522 is a medium-severity vulnerability in team-alembic ash_authentication, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-86522 and fix it if it is affected.\n\nWhat it is: CVE-2026-86522 is a medium-severity vulnerability in team-alembic ash_authentication, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-86522 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ash_authentication (Hex): affected from 4.2.0; fixed in 4.15.0, 5.0.0-rc.14\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-86522/ (Markdown: https://insights.sbomify.com/CVE-2026-86522/index.md)","id":"CVE-2026-86522","markdown":"https://insights.sbomify.com/CVE-2026-86522/index.md","name":"CVE-2026-86522","record":{"aliases":["EEF-CVE-2026-86522","GHSA-wg7g-r393-vr3g"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir authentication library","requires_auth":"none","summary":"An unauthenticated attacker can forge application log entries by injecting newlines into password reset identities, potentially misleading security monitoring.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"Improper Output Neutralization for Logs vulnerability in team-alembic AshAuthentication allows an unauthenticated attacker to forge application log entries by submitting a password reset identity containing newlines or control characters.\n\nAshAuthentication.Strategy.Password.RequestPasswordReset.run/3 interpolates the identity argument, the email or username taken straight from the reset request, into its Logger.warning/1 heredocs without escaping, truncating or type-restricting it. The resource logged beside it is passed through inspect/1, which would have neutralized the value. A newline in the identity therefore ends the log record, and everything after it is written as a line of its own, so an attacker chooses the severity tag and the content of entries that appear to have come from the application.\n\nThis issue affects ash_authentication: from 4.2.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Log injection via an unescaped password reset identity in AshAuthentication","id":"CVE-2026-86522","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"other","year":"2026"},"n_packages":1,"n_references":6,"next":{"headline":"Command injection in WEX-G300","id":"CVE-2026-86530"},"packages":[{"ecosystem":"Hex","fixed":["4.15.0","5.0.0-rc.14"],"introduced":["4.2.0","5.0.0-rc.0"],"last_affected":[],"package":"ash_authentication","purl":"pkg:hex/ash_authentication","source":"EEF-CVE-2026-86522"}],"prev":{"headline":"Use of Hard-coded Credentials in Bransys ELD","id":"CVE-2026-86520"},"products":["ash_authentication"],"published":"2026-09-17","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["team-alembic"]},"summary":"An unauthenticated attacker can forge application log entries by injecting newlines into password reset identities, potentially misleading security monitoring.","url":"https://insights.sbomify.com/CVE-2026-86522/"}