Quick answers
- Is CVE-2026-102490 exploited in the wild?
- Yes. CVE-2026-102490 is known to be exploited in the wild, first recorded on 2 October 2026. Treat it as urgent.
- How severe is CVE-2026-102490?
- Critical severity, published 30 September 2026.
- Which products and versions are affected?
- Zammad 6.3.0 to 6.5.4, 7.0.0 to 7.1.3.
- Is there a fix for CVE-2026-102490?
- 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-102490 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-102490?
- Check whether you run Zammad or Zammad Gmbh Zammad 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 session hijack flaw in Zammad that enables remote code execution with the privileges of the zammad application user. Versions 6.3.0–6.5.4 are directly exploitable; versions 7.0.0–7.1.3 contain the same code path but mitigating factors prevent practical exploitation. Attack vectors and preconditions are not detailed in available references, but the session hijacking mechanism likely allows unauthenticated or low-privilege attackers to assume valid sessions.
Affected products
- Zammad Zammad 6.3.0 to 6.5.4, 7.0.0 to 7.1.3
Identifiers
- CVE-2026-102490
- CVE-2026-102489
Timeline
- 2026-09-30: disclosed