{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68624 exists.","fix":"No fix has been published for CVE-2025-68624 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-68624 is a medium-severity missing authorization vulnerability in N-able Mail Assure, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-68624 and fix it if it is affected.\n\nWhat it is: CVE-2025-68624 is a medium-severity missing authorization vulnerability in N-able Mail Assure, published on 14 Sep 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-2025-68624 exists.\n\nAffected product: N-able Mail Assure. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-68624/ (Markdown: https://insights.sbomify.com/CVE-2025-68624/index.md)","id":"CVE-2025-68624","markdown":"https://insights.sbomify.com/CVE-2025-68624/index.md","name":"CVE-2025-68624","record":{"aliases":["GHSA-8wch-g3f4-9xpr"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["security_bypass","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Mail Assure","requires_auth":"low_privilege","summary":"Authenticated users can impersonate other tenants' domains in outbound emails, bypassing sender validation and potentially enabling phishing attacks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"N-able Mail Assure through April 2026 contains a design-level authorization flaw that allows an authenticated SMTP user to send outbound email using MAIL FROM addresses belonging to other tenants. When connecting to the SMTP TCP port and performing SMTP AUTH with valid credentials, the server accepts arbitrary sender domains without enforcing any domain-to-account binding. As a result, an attacker from any tenant can impersonate other tenant domains, producing messages that pass SPF and DMARC validation. NOTE: N-able's position is that the behavior is intended functionality of its shared SMTP relay architecture and that the service does not represent that it enforces per-tenant sender-domain binding.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Missing authorization in Mail Assure","id":"CVE-2025-68624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Apache Uniffle: Insecure SSL Configuration in Uniffle HTTP Client","id":"CVE-2025-68637"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-68623"},"products":["Mail Assure"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-17","vendors":["N-able"]},"summary":"Authenticated users can impersonate other tenants' domains in outbound emails, bypassing sender validation and potentially enabling phishing attacks.","url":"https://insights.sbomify.com/CVE-2025-68624/"}