Skip to main content
VulnerabilityPublished

CVE-2026-3563: Devolutions PowerShell Universal · Improper validation of unsafe equivalence in input

Affects Devolutions PowerShell UniversalSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 2026.1.4 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.1.4
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade Devolutions PowerShell Universal to 2026.1.4.

Affected software

ProductAffectedFixed in
DevolutionsPowerShell UniversalAffected
  • >=2026.1.0 <2026.1.4
Fixed in
  • 2026.1.4

AI-suggested

To mitigate CVE-2026-3563, organizations should: 1) Immediately restrict permissions for creating or modifying Apps or Endpoints in PowerShell Universal to only trusted administrators. 2) Monitor and audit changes to app and endpoint configurations to detect unauthorized or suspicious modifications. 3) Apply the official patch or upgrade to PowerShell Universal version 2026.1.4 or later as soon as it becomes available. 4) Implement multi-factor authentication and strong access controls to reduce the risk of credential compromise for users with modification privileges. 5) Use network segmentation and firewall rules to limit access to the PowerShell Universal management interfaces. 6) Conduct regular security reviews of automation and orchestration tools to identify and remediate configuration weaknesses. 7) Consider implementing runtime monitoring to detect anomalous routing behavior or denial of service conditions caused by conflicting URL paths. These steps go beyond generic advice by focusing on permission management, proactive monitoring, and timely patching specific to this vulnerability.

Description

Improper input validation in the apps and endpoints configuration in PowerShell Universal before 2026.1.4 allows an authenticated user with permissions to create or modify Apps or Endpoints to override existing application or system routes, resulting in unintended request routing and denial of service via a conflicting URL path.

References

Community reviews

Loading reviews…