Devolutions PowerShell Universal CVE-2026-16798

The attacker requires an authenticated account with scoped read permission on automation jobs or scripts within PowerShell Universal. The API must return job read responses that include the refresh token; this is a default behavior for affected versions when OAuth integrations are used. No network-level bypasses or unauthenticated access vectors exist. Exploitation is limited to information disclosure of OAuth tokens and does not directly compromise the application host.

CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N yields a medium 6.5 score, but EPSS predicts only a 0.22% chance of widespread exploitation (12th percentile). SSVC rates exploitation as none, automatable as no, and technical impact as partial. Real-world risk is low because exploitation requires authenticated read access to jobs or scripts, and only exposes a refresh token-not direct credentials. The vendor has released a patch in version 2026.2.3, further limiting residual risk. Contrastingly, the token could enable lateral movement to integrated OAuth services, but this secondary impact depends on the scope of the compromised token and is not factored into the primary confidentiality impact.

An attacker authenticates to PowerShell Universal with an account that has scoped read permissions to automation jobs. They enumerate the jobs API and retrieve job details, finding an OAuth refresh token for another user leaked in the response. The attacker then uses that token to authenticate to the victim's associated OAuth service (e.g., Azure, Git) and accesses protected resources.