{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-78359 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-78359 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-78359 is a medium-severity vulnerability in ((OTRS)) Community Edition, published on 12 Oct 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-78359 and fix it if it is affected.\n\nWhat it is: CVE-2026-78359 is a medium-severity vulnerability in ((OTRS)) Community Edition, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-78359 in the wild and no public exploit code.\n\nAffected product: ((OTRS)) Community Edition. 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-78359/ (Markdown: https://insights.sbomify.com/CVE-2026-78359/index.md)","id":"CVE-2026-78359","markdown":"https://insights.sbomify.com/CVE-2026-78359/index.md","name":"CVE-2026-78359","record":{"aliases":["GHSA-49rp-wmg4-84xg","UBUNTU-CVE-2026-78359"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"OTRS ticketing system","requires_auth":"low_privilege","summary":"Authenticated users with customer management permissions can create duplicate identities across backends, leading to data exposure or misrouting.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"OTRS","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-706","name":"Use of Incorrectly-Resolved Name or Reference"},{"id":"CWE-694","name":"Use of Multiple Resources with Duplicate Identifier"}],"description":"OTRS does not sufficiently enforce the uniqueness of customer user identities across multiple configured CustomerUser backends. When multiple backends, such as a database and LDAP, are configured, the uniqueness check for customer user email addresses is performed only within the selected backend. As a result, an authenticated user with permission to create or modify customer users may create a customer user whose email address is already assigned to a customer user in another backend.\n\nThis can result in multiple customer user records representing the same communication identity. Depending on the affected workflow and backend resolution, customer-related information or email communication may subsequently be associated with or exposed to the wrong customer user.\n\nThe vulnerability does not allow unauthenticated users to create customer accounts. Exploitation requires permissions to create or modify customer users.\n\nThis issue affects OTRS:\n\n  *  7.0.X\n  *  8.0.X\n  *  2023.X\n  *  2024.X\n  *  2025.X\n  *  2026.X before 2026.7.X\n\nPlease note that ((OTRS)) Community Edition 6.x and before are vulnerable. Products based on the ((OTRS)) Community Edition also very likely to be affected","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":"Duplicate Identity / Identity Shadowing across CustomerUser backends","id":"CVE-2026-78359","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"zipMoney(Zip Co) Payments Plugin for WooCommerce \u003c 2.4.0 - Unauthenticated Arbitrary Option Deletion","id":"CVE-2026-78361"},"packages":[],"prev":{"headline":"Cross-Site Request Forgery in Administrative Actions","id":"CVE-2026-78358"},"products":["((OTRS)) Community Edition","OTRS"],"published":"2026-10-12","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["OTRS GmbH (former OTRS AG)"]},"summary":"Authenticated users with customer management permissions can create duplicate identities across backends, leading to data exposure or misrouting.","url":"https://insights.sbomify.com/CVE-2026-78359/"}