CVE-2026-0618: Devolutions PowerShell Universal · XSS or 'Cross-site Scripting'
Affects Devolutions PowerShell UniversalSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium : upgrade to 5.6.13 or 4.5.6 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.6.13, 4.5.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade Devolutions PowerShell Universal to 5.6.13 or 4.5.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DevolutionsPowerShell Universal | Affected
| Fixed in
|
AI-suggested
1. Immediately inventory all instances of Devolutions PowerShell Universal within the organization to identify affected versions. 2. Monitor Devolutions’ official channels for the release of patches addressing CVE-2026-0618 and apply updates promptly once available. 3. Implement strict input validation and output encoding on any custom scripts or extensions interacting with the PowerShell Universal web interface to reduce injection risks. 4. Employ Web Application Firewalls (WAFs) with rules designed to detect and block common XSS payloads targeting PowerShell Universal endpoints. 5. Restrict access to the PowerShell Universal web interface to trusted networks and authenticated users only, using network segmentation and VPNs where feasible. 6. Conduct regular security awareness training for administrators and users to recognize suspicious URLs or unexpected web content. 7. Enable logging and monitoring of web interface access and unusual script execution activities to detect potential exploitation attempts early. 8. Consider implementing Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers accessing the application.
Description
Cross-site Scripting vulnerability in Devolutions PowerShell Universal.This issue affects Powershell Universal: before 4.5.6, before 5.6.13.