{"answers":{"affected":"2 open source packages ship an affected version, including ash_authentication.","exploited":"There is no known exploitation of CVE-2025-32782 in the wild and no public exploit code.","fix":"Upgrade ash_authentication to 4.7.0 or later.","what":"CVE-2025-32782 is a medium-severity vulnerability in team-alembic ash_authentication, published on 15 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32782 and fix it if it is affected.\n\nWhat it is: CVE-2025-32782 is a medium-severity vulnerability in team-alembic ash_authentication, published on 15 Apr 2025. 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-2025-32782 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ash_authentication (Hex): affected all versions; fixed in 4.7.0\n- ash_authentication (Hex): affected all versions; fixed in 4.7.0\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-2025-32782/ (Markdown: https://insights.sbomify.com/CVE-2025-32782/index.md)","id":"CVE-2025-32782","markdown":"https://insights.sbomify.com/CVE-2025-32782/index.md","name":"CVE-2025-32782","record":{"aliases":["GHSA-3988-q8q7-p787"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir authentication library","requires_auth":"none","summary":"Attackers can register accounts using victim emails that are auto-confirmed by email clients, bypassing manual verification steps.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Ash Authentication provides authentication for the Ash framework. The confirmation flow for account creation currently uses a GET request triggered by clicking a link sent via email. Some email clients and security tools (e.g., Outlook, virus scanners, and email previewers) may automatically follow these links, unintentionally confirming the account. This allows an attacker to register an account using another user’s email and potentially have it auto-confirmed by the victim’s email client. This does not allow attackers to take over or access existing accounts or private data. It is limited to account confirmation of new accounts only. This vulnerability is fixed in 4.7.0.","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":"Ash Authentication email link auto-click account confirmation vulnerability","id":"CVE-2025-32782","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"XWiki allows unregistered users to see \"public\" messages from a closed wiki via notifications from a different wiki","id":"CVE-2025-32783"},"packages":[{"ecosystem":"Hex","fixed":["4.7.0"],"introduced":["0"],"last_affected":[],"package":"ash_authentication","purl":null,"source":"GHSA-3988-q8q7-p787"},{"ecosystem":"Hex","fixed":["4.7.0"],"introduced":["0"],"last_affected":[],"package":"ash_authentication","purl":"pkg:hex/ash_authentication","source":"GHSA-3988-q8q7-p787"}],"prev":{"headline":"Apollo: Apollo Portal release endpoint allows cross-application configuration disclosure via releaseId","id":"CVE-2025-32781"},"products":["ash_authentication"],"published":"2025-04-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"2025-04-16","vendors":["team-alembic"]},"summary":"Attackers can register accounts using victim emails that are auto-confirmed by email clients, bypassing manual verification steps.","url":"https://insights.sbomify.com/CVE-2025-32782/"}