Skip to main content
Vulnerability Database/CVE-2026-78359

CVE-2026-78359: OTRS Authentication Bypass Vulnerability

CVE-2026-78359 is an authentication bypass flaw in OTRS that allows authenticated users to create duplicate customer identities across multiple backends. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-78359 Overview

CVE-2026-78359 is a business logic flaw in OTRS that fails to enforce uniqueness of customer user email addresses across multiple configured CustomerUser backends. When OTRS is configured with more than one backend, such as a database alongside Lightweight Directory Access Protocol (LDAP), the uniqueness check runs only within the selected backend. An authenticated operator with permission to create or modify customer users can register a customer user whose email address already exists in another backend. The result is duplicate customer records tied to the same communication identity, which may route tickets, replies, or disclosed information to the wrong account.

Critical Impact

Duplicate customer identities across backends may cause customer data and email correspondence to be exposed to or associated with the wrong customer user, breaking tenant and identity boundaries within OTRS.

Affected Products

  • OTRS versions 7.0.X, 8.0.X, 2023.X, 2024.X, 2025.X, and 2026.X before 2026.7.X
  • ((OTRS)) Community Edition 6.x and earlier
  • Products derived from the ((OTRS)) Community Edition codebase

Discovery Timeline

  • 2026-10-12 - CVE-2026-78359 published to the National Vulnerability Database (NVD)
  • 2026-10-15 - Last updated in NVD database

Technical Details for CVE-2026-78359

Vulnerability Analysis

OTRS supports multiple customer user sources through its CustomerUser backend configuration. Administrators commonly layer a local database backend with one or more directory backends such as LDAP. The identity model relies on email addresses as the stable, cross-system identifier for a customer contact. When new customer users are created or modified, OTRS verifies that the email address is unique, but this check is scoped only to the currently selected backend.

This scoping gap allows an authenticated user with customer management rights to introduce a second record for an email address that already exists in another backend. Depending on which backend wins resolution for a given workflow, incoming email, ticket assignment, or lookup by address can bind to the wrong account. The flaw is tracked under [CWE-694: Use of Multiple Resources with Duplicate Identifier].

Root Cause

The root cause is incomplete validation logic. The uniqueness enforcement for the customer user email attribute executes against a single backend scope rather than the full set of configured CustomerUser sources. OTRS trusts each backend as an independent identity namespace, so two distinct records can legitimately share the same email identifier.

Attack Vector

Exploitation requires an authenticated session with permissions to create or modify customer users. The attacker enumerates or guesses an existing email address resident in one backend, then creates a conflicting customer user in a different backend. Subsequent lookups, ticket creation from incoming mail, or agent searches may resolve to the attacker-controlled record, leaking customer information or redirecting communication. Unauthenticated account creation is not possible.

See the OTRS Security Advisory 2026-16 for vendor technical details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-78359

Indicators of Compromise

  • Multiple customer user records sharing the same email address but originating from different CustomerUser backends.
  • Unexpected creation or modification events for customer users performed by accounts that rarely use that privilege.
  • Tickets or email correspondence being associated with a customer user that does not match the historical account for a given email address.

Detection Strategies

  • Query each configured CustomerUser backend for duplicate email values and cross-correlate the result sets to find collisions.
  • Audit the OTRS admin interface logs for CustomerUserAdd and CustomerUserUpdate actions targeting email addresses already present in another backend.
  • Review agent audit trails for customer users whose backend source changes between related tickets.

Monitoring Recommendations

  • Monitor privileged OTRS operator accounts for customer user creation activity and alert on bursts of new entries.
  • Track mail-to-ticket routing decisions and flag cases where the resolved customer user differs from the historical mapping for the sender address.
  • Forward OTRS application and admin audit logs to a centralized logging or SIEM platform and build correlation rules on duplicate email identifiers across backends.

How to Mitigate CVE-2026-78359

Immediate Actions Required

  • Upgrade OTRS to 2026.7.X or later, which contains the fix referenced in OTRS Security Advisory 2026-16.
  • Review and reduce the set of agents and administrators holding permission to create or modify customer users.
  • Perform a one-time reconciliation across all configured CustomerUser backends to identify and remediate existing duplicate email entries.

Patch Information

OTRS has released a fix in the 2026.7.X branch. All supported branches listed as affected (7.0.X, 8.0.X, 2023.X, 2024.X, 2025.X, 2026.X before 2026.7.X) should receive the corresponding vendor update. ((OTRS)) Community Edition 6.x and derived products are vulnerable and do not have a vendor patch path; migration or compensating controls are required.

Workarounds

  • Operate with a single CustomerUser backend where feasible to eliminate cross-backend collisions.
  • Restrict customer user creation and modification privileges to a minimal, audited group of administrators.
  • Implement an out-of-band reconciliation job that scans all backends for duplicate email values and quarantines conflicts for manual review.
bash
# Configuration example
# Review configured CustomerUser backends in Kernel/Config.pm
# Reduce to a single authoritative source where possible
$Self->{CustomerUser} = {
    Name   => 'Database Backend',
    Module => 'Kernel::System::CustomerUser::DB',
    # Additional backends (CustomerUser1, CustomerUser2) increase exposure
};

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.