{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-84458 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-84458 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-84458 is a critical authentication bypass vulnerability in zammad, published on 25 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-84458 and fix it if it is affected.\n\nWhat it is: CVE-2026-84458 is a critical authentication bypass vulnerability in zammad, published on 25 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-84458 in the wild and no public exploit code.\n\nAffected product: zammad. 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-2026-84458/ (Markdown: https://insights.sbomify.com/CVE-2026-84458/index.md)","id":"CVE-2026-84458","markdown":"https://insights.sbomify.com/CVE-2026-84458/index.md","name":"CVE-2026-84458","record":{"aliases":["GHSA-86cc-3ggh-mf2m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Zammad helpdesk","requires_auth":"none","summary":"Attackers can take over accounts by exploiting unverified email matching during SSO auto-linking when the automatic account link setting is enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when the \"Automatic account link on initial logon\" setting is enabled, Zammad binds an incoming third-party (SSO) identity to an existing local account by matching the email address the identity provider reports, without verifying that the provider actually confirmed ownership of that email. An attacker who controls any identity at a configured provider, including, by default, any Azure AD tenant via Zammad's multi-tenant Microsoft 365 /common app registration, can set that identity's email to a victim's address, authenticate, and be logged in as the victim. This bypasses the victim's local password entirely and affects any existing account, including agents and administrators. Zammad will honor the xms_edov ID token claim when email verification is required in the Microsoft 365 setting, treating a missing claim as unverified. This issue is fixed in version 7.1.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Zammad: Account takeover via unverified email matching during SSO auto-link","id":"CVE-2026-84458","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Zammad: Missing Authorization in TagsController#list Allows Cross-Object Tag Enumeration","id":"CVE-2026-84460"},"packages":[],"prev":{"headline":"Windows ML CLI: CORS misconfig enables localhost RCE","id":"CVE-2026-84452"},"products":["zammad"],"published":"2026-09-25","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-25","vendors":["zammad"]},"summary":"Attackers can take over accounts by exploiting unverified email matching during SSO auto-linking when the automatic account link setting is enabled.","url":"https://insights.sbomify.com/CVE-2026-84458/"}