CVE-2026-78357
waiting for further signalsZero needs more public information before it can validate it.GHSA-f6jh-p427-pjq6 ↗EUVD-2026-97267 ↗
description
OTRS 7.0.X, 8.0.X, and 2023.X through 2026.X before 2026.7.X may continue accepting issued login tokens after the associated account is disabled or its password is changed. An attacker who already possesses an unexpired token can continue operating with that account's permissions until the token expires.
mitigation
Upgrade OTRS 2026.X to 2026.7.X or later. For affected branches without a recorded fixed release, limit access for accounts with suspected token exposure and obtain an updated release from the supplier.
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-12 06:49Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-78357
{ "etk_id": "ETK-2026-1321", "cve_id": "CVE-2026-78357", "display_id": "CVE-2026-78357", "ghsa_id": "GHSA-f6jh-p427-pjq6", "euvd_id": "EUVD-2026-97267", "status": "published", "anchor_state": "anchored", "title": "OTRS authentication token revocation failure", "summary": "OTRS 7.0.X, 8.0.X, and 2023.X through 2026.X before 2026.7.X may continue accepting issued login tokens after the associated account is disabled or its password is changed. An attacker who already possesses an unexpired token can continue operating with that account's permissions until the token expires.", "mitigation": "Upgrade OTRS 2026.X to 2026.7.X or later. For affected branches without a recorded fixed release, limit access for accounts with suspected token exposure and obtain an updated release from the supplier.", "vendor": "OTRS GmbH (former OTRS AG)", "product": "OTRS", "affected": [ { "affected_notes": [], "affected_ranges": [ "7.0.x", "8.0.x", "2023.x", "2024.x", "2025.x", ">= 2026.x, <= 2026.6.x" ], "ecosystem": null, "fixed_versions": [], "package_name": "OTRS", "purl": null } ], "cwes": [ 613 ], "cvss_score": 9.1, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "epss_score": 0.003, "epss_percentile": 0.2184, "epss_asof": "2026-10-20", "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 16.0947729, "t0_at": "2026-10-12T06:49:10.919000+00:00", "signals": { "trigger_signal": { "at": "2026-10-12T06:49:10.919000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-12T06:49:10.919000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-78357" } } }
published 2026-10-12 07:26Z
last change 2026-10-21 04:45Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.