CVE-2026-78359
MEDIUMDescription
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
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 6% of all known CVEs.
References
Related Vulnerabilities
Other CWE-694 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-15187 | Low | 3.0 | 1.5% | - | Fix |
| CVE-2021-3436 | Medium | 4.3 | 1.0% | - | - |
| CVE-2020-15185 | Low | 2.2 | 0.9% | - | Fix |
| CVE-2023-20100 | Medium | 6.8 | 0.8% | - | - |
| CVE-2026-102634 | High | 7.5 | 0.6% | - | - |
| CVE-2026-63976 | High | 8.8 | 0.6% | - | Fix |
Common questions
How do I fix CVE-2026-78359?
No published fix for CVE-2026-78359 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-78359 being actively exploited?
Not that we know of. CVE-2026-78359 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.16% is the estimated probability that it will be exploited in the next 30 days. That is higher than 6% of all scored CVEs.
How severe is CVE-2026-78359?
CVE-2026-78359 has a CVSS v3 base score of 5.4, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-78359
Markdown
[](https://tridentstack.com/cve/CVE-2026-78359)HTML
<a href="https://tridentstack.com/cve/CVE-2026-78359"><img src="https://tridentstack.com/cve/badge/CVE-2026-78359.svg" alt="CVE-2026-78359"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-15.