CVE-2026-16801
Authenticated code injection in Devolutions PowerShell Universal (≤2026.2.2).
Is CVE-2026-16801 being exploited?
Not confirmed. CVE-2026-16801 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-16801?
CVE-2026-16801 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-16801?
Yes. A fix has been recorded for CVE-2026-16801. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16801 affect?
CVE-2026-16801 affects Devolutions PowerShell Universal ≤ 2026.2.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16801?
Apply vendor patch when released; immediately restrict variable-write permissions and audit variables.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated user with variable-write permission can execute arbitrary PowerShell on the server (RCE, data and credential theft).
Immediate action required
- affected< 2026.2.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.