Quick answers
- Is CVE-2026-9226 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-9226 being exploited in the wild.
- How severe is CVE-2026-9226?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Devolutions Server 2026.3.7.0 and earlier.
- Is there a fix for CVE-2026-9226?
- 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-9226 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-9226?
- 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 vulnerability is a token replay flaw in the Azure AD external login flow where session tokens are exposed in redirect URLs. An attacker who captures the redirect URL during a login attempt can reuse the token to authenticate as that user without credentials. This affects Devolutions Server 2026.3.7.0 and earlier.
Affected products
- Devolutions Server 2026.3.7.0 and earlier
Timeline
- 2026-10-06: disclosed