Insufficient session revocation in OTRS lets old tokens stay valid
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-613.
Summary
OTRS GmbH's OTRS versions 7.0.x, 8.0.x, 2023.x, 2024.x, 2025.x and 2026.x through 2026.6.x are affected. Previously issued JWT authentication tokens stay valid after an agent or customer user account is deactivated or its password is changed (CWE-613). An attacker who already holds a valid token can keep accessing OTRS with that user's privileges until the token expires, which can take approximately 16 hours.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
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
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| OTRS GmbH (former OTRS AG) | OTRS | 7.0.x; 8.0.x; 2023.x; 2024.x; 2025.x; 2026.x – 2026.6.x | — | No fix listed | CNA |
- OTRS VendorOTRS GmbH (former OTRS AG) Affected 7.0.x; 8.0.x; 2023.x; 2024.x; 2025.x; 2026.x – 2026.6.x Fixed in — No fix listed CNA
Remediation
The sources list no fixed version for OTRS.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Timeline
- 2026-10-12 Threatist record created from CVE-2026-78357
- 2026-10-12 Alias added: GHSA-f6jh-p427-pjq6
- 2026-10-12 Priority changed: MEDIUM → LOW
- 2026-10-16 CISA SSVC decision points changed
- 2026-10-16 Priority changed: LOW → MEDIUM
References
More OTRS GmbH (former OTRS AG) vulnerabilities
- TI-2026-70873 Authentication bypass via spoofed Remote-User header in OTRS CVSS 3.1CRITICAL 9.4
- TI-2026-70864 Path traversal in OTRS SendSupportBundle allows file deletion CVSS 3.1HIGH 8.7
- TI-2026-70865 Unauthenticated disclosure of OTRS Agent Frontend configuration CVSS 3.1MEDIUM 5.3
- TI-2026-70872 Formula injection in OTRS CSV exports CVSS 3.1MEDIUM 6.1
- TI-2026-70868 Duplicate customer identities across backends in OTRS CVSS 3.1MEDIUM 5.4
- TI-2026-70862 Cross-site request forgery in OTRS Import/Export admin console CVSS 3.1MEDIUM 5.4
Sources
- CVE-2026-78357 · CVE Program
- CVE-2026-78357 · NVD
- FIRST EPSS
- GHSA-f6jh-p427-pjq6 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences