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.

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
Published: 2026-10-12
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Duplicated customer identities leading to incorrect data association or exposure
Action: Apply Patch
AI Analysis

Impact

The flaw in OTRS occurs when multiple CustomerUser backends are configured, such as a database and LDAP, because the system performs the uniqueness check for customer user email addresses only within the selected backend. An authenticated user with permission to create or modify customer users can therefore create a new customer record whose email address already exists in another backend. This results in duplicate customer user records that symbolize the same communication identity. Consequently, customer‑related data or e‑mail communication may be delivered to or exposed through the wrong customer account. The vulnerability cannot be exploited by unauthenticated users; attacker must have the privilege to add or edit customers.

Affected Systems

The affected products are OTRS Community Edition 6.x and earlier, plus OTRS GmbH Community Edition 7.0.X, 8.0.X, 2023.X, 2024.X, 2025.X and 2026.X versions prior to 2026.7.X. Because product families based on the Community Edition are also likely affected, any derivative installations built upon those versions should be treated as vulnerable.

Risk and Exploitability

The CVSS score of 5.4 reflects moderate severity. With no EPSS data, the likelihood of compromise is unclear, but the fact that the issue is only exploitable by users already granted customer‑account creation rights means that attacker privilege escalation is required. The vulnerability is not listed in CISA's KEV catalog. The attack vector is limited to authenticated users within the system who can add or modify customer users; an attacker would need to gain such permissions either by compromising an existing privileged account or by escalating privileges within OTRS.

Generated by OpenCVE AI on October 12, 2026 at 08:23 UTC.

Remediation

Vendor Solution

Update to latest version of OTRS (2026.7.1. or later). Please note that there will be no OTRS 7 patches


OpenCVE Recommended Actions

  • Upgrade OTRS to version 2026.7.1 or later, which fixes the cross‑backend uniqueness enforcement.
  • Limit permissions so that only trusted administrators can create or modify CustomerUser records; apply the principle of least privilege to these capabilities.
  • Review existing customer user accounts for duplicate email addresses across backends and reconcile or delete the duplicates to prevent data misassociation.

Generated by OpenCVE AI on October 12, 2026 at 08:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 12 Oct 2026 07:00:00 +0000

Type Values Removed Values Added
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. 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
Title Duplicate Identity / Identity Shadowing across CustomerUser backends
Weaknesses CWE-694
CWE-706
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: OTRS

Published:

Updated: 2026-10-12T06:49:24.983Z

Reserved: 2026-08-24T11:29:41.427Z

Link: CVE-2026-78359

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-12T07:16:37.423

Modified: 2026-10-12T07:16:37.423

Link: CVE-2026-78359

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-12T08:30:07Z

Weaknesses
  • CWE-694

    Use of Multiple Resources with Duplicate Identifier

  • CWE-706

    Use of Incorrectly-Resolved Name or Reference