Description
Previously issued authentication tokens are not immediately invalidated when an OTRS agent or customer user account is deactivated or its password is changed. As a result, an existing JWT may remain valid until its regular expiration time, which can be approximately 16 hours.

An attacker who has previously obtained a valid authentication token can therefore continue to access OTRS with the privileges of the affected agent or customer user even after the corresponding account has been deactivated or the user's password has been changed.

The vulnerability does not allow an attacker to obtain authentication tokens by itself. Exploitation requires possession of a previously issued and still valid token. The actual impact depends on the privileges associated with the compromised token. Customer user tokens are limited to the permissions of the affected customer account, while agent tokens may provide access to broader ticket, customer, or administrative functionality depending on the assigned permissions.

This issue affects OTRS:

* 7.0.X
* 8.0.X
* 2023.X
* 2024.X
* 2025.X
* 2026.X before 2026.7.X
Published: 2026-10-12
Score: 9.1 Critical
EPSS: n/a
KEV: No
Impact: Unauthorized access with retained privileges
Action: Immediate Patch
AI Analysis

Impact

This is a flaw in OTRS that allows a previously issued JSON Web Token (JWT) to remain valid after its associated user account is either deactivated or its password changed. Because the token is not revoked immediately, an attacker who already holds a valid token can continue to use that token to access OTRS services for up to the token’s remaining lifetime—potentially 16 hours. The impact depends on the token’s privileges: an agent token could grant broader ticket or administrative access, while a customer token is confined to the customer’s own permissions. The vulnerability does not grant new tokens; it only affords extended use of an existing one.

Affected Systems

The vulnerability affects OTRS from OTRS GmbH. Versions impacted include 7.0.X, 8.0.X, and the 2023, 2024, 2025 and 2026 line releases up to but excluding 2026.7.X. The vendor’s fix is to upgrade to OTRS 2026.7.1 or any later release.

Risk and Exploitability

The CVSS score of 9.1 classifies this issue as high severity. EPSS data is not available, but a prolonged exploitation window exists because a valid token can stay active for many hours. Exploitation requires an attacker to have received a legitimate token beforehand, typically via prior compromise or credential theft; once obtained, the token can be used for unauthorized access until it expires or until the account is revived again. The vulnerability is not listed in CISA’s KEV catalog, yet the potential for extended unauthorized access warrants treating the issue as a critical risk, especially in environments with long token lifetimes.

Generated by OpenCVE AI on October 12, 2026 at 08:24 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

  • Apply the latest OTRS 2026.7.1 or later to install the vendor‑supplied revocation fix.
  • Review all outstanding JWTs and revoke any that belong to deactivated or password‑changed accounts, ensuring that tokens are invalidated immediately when an account status changes.
  • Reduce the maximum JWT lifespan or enforce custom revocation logic so that tokens associated with deactivated accounts are invalidated as soon as possible; consider automated token rotation or a tighter expiration policy and monitor logs for anomalous token usage.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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

Type Values Removed Values Added
First Time appeared Otrs
Otrs otrs
Vendors & Products Otrs
Otrs otrs

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

Type Values Removed Values Added
Description Previously issued authentication tokens are not immediately invalidated when an OTRS agent or customer user account is deactivated or its password is changed. As a result, an existing JWT may remain valid until its regular expiration time, which can be approximately 16 hours. An attacker who has previously obtained a valid authentication token can therefore continue to access OTRS with the privileges of the affected agent or customer user even after the corresponding account has been deactivated or the user's password has been changed. The vulnerability does not allow an attacker to obtain authentication tokens by itself. Exploitation requires possession of a previously issued and still valid token. The actual impact depends on the privileges associated with the compromised token. Customer user tokens are limited to the permissions of the affected customer account, while agent tokens may provide access to broader ticket, customer, or administrative functionality depending on the assigned permissions. This issue affects OTRS: * 7.0.X * 8.0.X * 2023.X * 2024.X * 2025.X * 2026.X before 2026.7.X
Title Insufficient Session Revocation for JWT Authentication
Weaknesses CWE-613
References
Metrics cvssV3_1

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


cve-icon MITRE

Status: PUBLISHED

Assigner: OTRS

Published:

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

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

Link: CVE-2026-78357

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

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

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

Link: CVE-2026-78357

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-12T08:45:09Z

Weaknesses
  • CWE-613

    Insufficient Session Expiration