Quick answers
- Is CVE-2026-78357 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78357 being exploited in the wild.
- How severe is CVE-2026-78357?
- Critical severity, with a CVSS score of 9.1, published 12 October 2026.
- Which products and versions are affected?
- Otrs 7.0.x, 8.0.x, 2023.x, 2024.x, 2025.x, 2026.x before 2026.7.x.
- Is there a fix for CVE-2026-78357?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-78357 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-78357?
- Check whether you run Otrs at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a token invalidation failure in OTRS authentication: JWT tokens are not revoked when an associated agent or customer account is deactivated or when a password change occurs, allowing token reuse until natural expiration at ~16 hours. Exploitation requires prior possession of a valid token and does not grant the attacker ability to generate new tokens; impact scales with the privileges of the compromised account (customer users face limited exposure, agents may face broader ticket/administrative access loss).
Affected products
- OTRS OTRS 7.0.x, 8.0.x, 2023.x, 2024.x, 2025.x, 2026.x before 2026.7.x
Timeline
- 2026-10-12: disclosed