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.
This 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.
The vulnerability does not allow unauthenticated users to create customer accounts. Exploitation requires permissions to create or modify customer users.
This issue affects OTRS:
* 7.0.X
* 8.0.X
* 2023.X
* 2024.X
* 2025.X
* 2026.X before 2026.7.X
Please note that ((OTRS)) Community Edition 6.x and before are vulnerable. Products based on the ((OTRS)) Community Edition also very likely to be affected
Severity
CVSS 3.1
5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2%(unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-694Use of Multiple Resources with Duplicate Identifier CWE-706Use of Incorrectly-Resolved Name or Reference
Show the promptExplain CVE-2026-78359 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78359?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78359?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-78359 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
otrs gmbh (former otrs ag):((otrs)) community edition
otrs gmbh (former otrs ag):otrs
Versions
From the CNA's record in the CVE List.
Product
Affected
OTRS GmbH (former OTRS AG) OTRS
7.0.x
OTRS GmbH (former OTRS AG) OTRS
8.0.x
OTRS GmbH (former OTRS AG) OTRS
2023.x
OTRS GmbH (former OTRS AG) OTRS
2024.x
OTRS GmbH (former OTRS AG) OTRS
2025.x
OTRS GmbH (former OTRS AG) OTRS
from 2026.x through 2026.6.x
OTRS GmbH (former OTRS AG) ((OTRS)) Community Edition