CVE-2026-78359: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-49rp-wmg4-84xg
Share
CVSS 5.4
CWE-694
Published
Advisory Summary

CVE-2026-78359 is a MODERATE (CVSS 5.4) security vulnerability vulnerability (CWE-694: Use of Multiple Resources with Duplicate Identifier) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-78359 at a Glance

CVE Identifier CVE-2026-78359
GHSA Identifier GHSA-49rp-wmg4-84xg
Severity MODERATE
CVSS v3.1 Base Score 5.4
CWE Classification CWE-694: Use of Multiple Resources with Duplicate Identifier
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-78359

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-78359, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-694: Use of Multiple Resources with Duplicate Identifier, where the product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

References

NVD — CVE-2026-78359 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-78359
Software Release RELEASE
https://otrs.com/release-notes/otrs-security-advisory-2026-16

Frequently Asked Questions

What is CVE-2026-78359?
CVE-2026-78359 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-694: Use of Multiple Resources with Duplicate Identifier.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-78359?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-78359?
CVE-2026-78359 has a CVSS v3.1 base score of 5.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-78359?
CVE-2026-78359 is classified under CWE-694: Use of Multiple Resources with Duplicate Identifier (The product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.).
How can I check Maven dependencies for CVE-2026-78359?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-49rp-wmg4-84xg",
  "modified" : "2026-10-12T09:31:21Z",
  "published" : "2026-10-12T09:31:21Z",
  "aliases" : [ "CVE-2026-78359" ],
  "details" : "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",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-78359"
  }, {
    "type" : "WEB",
    "url" : "https://otrs.com/release-notes/otrs-security-advisory-2026-16"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-694" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-12T07:16:37Z"
  }
}