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

> Attackers with valid JWTs retain access after account deactivation or password changes, bypassing session revocation mechanisms in OTRS.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-f6jh-p427-pjq6, UBUNTU-CVE-2026-78357

## What is CVE-2026-78357?

CVE-2026-78357 is a critical vulnerability in OTRS, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-78357?


## How do I fix CVE-2026-78357?

No fix has been published for CVE-2026-78357 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-78357 being exploited?

There is no known exploitation of CVE-2026-78357 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78357 and fix it if it is affected.

What it is: CVE-2026-78357 is a critical vulnerability in OTRS, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78357 in the wild and no public exploit code.

Affected product: OTRS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-78357/ (Markdown: https://insights.sbomify.com/CVE-2026-78357/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78357
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78357
- OSV: https://osv.dev/vulnerability/CVE-2026-78357

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-78357/
Summaries are generated and may contain mistakes; the official description above is the record.