CVE-2026-78357: Insufficient Session Revocation for JWT Authentication

Published Oct 12, 2026
·
Updated

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

Affected Software

1 affected component
OTRS OTRS=7.0.X, =8.0.X, =2023.X, =2024.X, =2025.X, <2026.7.X

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OTRS to a version that resolves this vulnerability.

    Fixed in 2026.7.1

Event History

Oct 12, 2026
CVE Published
via MITRE·06:49 AM
Data Sourced
via MITRE·06:49 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to continued access after an account is disabled or its password is changed?

Any deactivated agent or customer user whose JWT was previously obtained may remain accessible until that token reaches its normal expiration, which can be approximately 16 hours. The resulting access is limited by the permissions assigned to the affected account.

2

What does an attacker need to exploit this issue?

The attacker must already possess a valid, previously issued JWT for the affected agent or customer user. This issue does not itself provide a way to obtain authentication tokens.

3

Are all affected tokens equally impactful?

No. Customer user tokens are limited to the affected customer account's permissions, while agent tokens may allow broader ticket, customer, or administrative access depending on the agent's assigned permissions.

4

How long can a compromised token remain usable after revocation-related actions?

A previously issued token can remain valid until its regular expiration time, which can be approximately 16 hours. Deactivating the account or changing its password does not immediately invalidate that token.

5

Which OTRS releases are affected?

Affected releases are OTRS 7.0.X, 8.0.X, 2023.X, 2024.X, 2025.X, and 2026.X before 2026.7.X.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203