Quick answers
- Is CVE-2026-119636 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119636 being exploited in the wild.
- How severe is CVE-2026-119636?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- Devolutions Server 2025.3.2.0 through 2026.2.2.
- Is there a fix for CVE-2026-119636?
- 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-119636 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-119636?
- Check whether you run Devolutions Server 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 PAM scheduled check-in task fails to properly release expired privileged account checkouts when a backlog of 21 or more newer active checkouts exists, preventing the expired checkout from being revoked and its password from being rotated. This is a logic flaw in the checkout lifecycle management that requires the attacker to already have checkout rights on the target account and allows them to retain credentials indefinitely until the backlog clears.
Affected products
- Devolutions Server 2025.3.2.0 through 2026.2.2
Timeline
- 2026-11-03: disclosed