Quick answers
- Is CVE-2026-16798 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16798 being exploited in the wild.
- How severe is CVE-2026-16798?
- Informational severity, with a CVSS score of 0, published 24 July 2026.
- Which products and versions are affected?
- Devolutions PowerShell Universal 2026.2.2 and earlier.
- Is there a fix for CVE-2026-16798?
- 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-16798 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-16798?
- Check whether you run Devolutions PowerShell Universal 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
An information disclosure vulnerability (CWE-201) exists in the automation jobs API of Devolutions PowerShell Universal. The root cause is a failure to strip sensitive OAuth refresh tokens from API responses when a user requests job details. An authenticated attacker with scoped 'job read' or 'script read' permissions can exploit this to obtain the refresh tokens of other users. This could lead to session hijacking or unauthorized access to third-party services integrated via OAuth. The issue is fixed in version 2026.2.3.
Affected products
- Devolutions PowerShell Universal 2026.2.2 and earlier
Timeline
- 2026-07-24: disclosed
- 2026-07-24: advisory