Quick answers
- Is CVE-2026-16800 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16800 being exploited in the wild.
- How severe is CVE-2026-16800?
- Informational severity, with a CVSS score of 7.7, 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-16800?
- A patch was published on 2026-07-24: Fixed in version 2026.2.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-16800 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-16800?
- 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
A code injection vulnerability exists in the schedule feature of Devolutions PowerShell Universal versions 2026.2.2 and earlier. The flaw is caused by improper control of code generation when schedule parameter names are concatenated into a script invocation without sufficient sanitization. An authenticated attacker with permissions to create schedules can exploit this by crafting malicious parameter names to execute arbitrary PowerShell code. This vulnerability is tracked as CVE-2026-16800 and has been addressed in version 2026.2.3.
Affected products
- Devolutions PowerShell Universal 2026.2.2 and earlier
Timeline
- 2026-07-24: disclosed
- 2026-07-24: advisory
- 2026-07-24: patched: Fixed in version 2026.2.3