VulnerabilityPublished 17 Mar 2026

CVE-2026-4064: Devolutions PowerShell Universal · Missing Authorization

Affects Devolutions PowerShell UniversalSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 2026.1.4 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

8.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% 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:L/UI:N/S:U/C:H/I:H/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Devolutions PowerShell Universal to 2026.1.4.

Affected software

Product	Affected	Fixed in
DevolutionsPowerShell Universal	Affected >=2026.1.0 <2026.1.4	Fixed in 2026.1.4

AI-suggested

To mitigate CVE-2026-4064, organizations should prioritize upgrading PowerShell Universal to version 2026.1.4 or later once the patch is released by Devolutions. If you cannot patch yet, organizations should enforce strict access controls on authentication tokens, ensuring that only trusted users have valid tokens. Implement network segmentation and firewall rules to restrict access to gRPC service endpoints to only necessary systems and users. Monitor logs and network traffic for unusual gRPC requests or privilege escalation attempts. Employ multi-factor authentication (MFA) to reduce the risk of token compromise. Review and audit role assignments and token issuance processes to minimize the number of users with valid tokens. Consider deploying runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to detect anomalous behavior related to unauthorized resource manipulation. Finally, maintain an incident response plan that includes scenarios involving privilege escalation and unauthorized access within automation platforms.

Description

Missing authorization checks on multiple gRPC service endpoints in PowerShell Universal before 2026.1.4 allows an authenticated user with any valid token to bypass role-based access controls and perform privileged operations — including reading sensitive data, creating or deleting resources, and disrupting service operations — via crafted gRPC requests.

Impact

The impact of CVE-2026-4064 is significant for organizations using affected versions of PowerShell Universal. Attackers who gain access with any valid token can escalate privileges beyond their intended scope, potentially accessing sensitive configuration data, credentials, or operational secrets. They can also create or delete resources, which may disrupt automated workflows, cause service outages, or corrupt system states. The ability to bypass RBAC undermines trust in the security model of the application and increases the risk of insider threats or compromised accounts being leveraged for lateral movement. Organizations in sectors relying heavily on automation and orchestration—such as finance, healthcare, government, and critical infrastructure—face increased risks of operational disruption and data breaches. The lack of known exploits in the wild reduces immediate risk but does not diminish the urgency to remediate, as the vulnerability is straightforward to exploit once an attacker has authenticated access. The scope of affected systems is limited to deployments of PowerShell Universal before version 2026.1.4, but given the product's use in enterprise environments worldwide, the potential impact is broad.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

devolutions.net/security/advisories/DEVO-2026-0008 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Mar 2026, 20:04 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats