CVE-2026-3130: Devolutions Server · Improper Enforcement of Behavioral Workflow
Affects Devolutions ServerSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 2025.3.16 as a priority.
Data as of 29 Oct 2026, 19:04 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2025.3.16
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 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.
What to do
Upgrade Devolutions Server to 2025.3.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| DevolutionsServer | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-3130, organizations should implement the following specific measures: 1) Restrict delete permissions strictly to trusted administrators and regularly audit permission assignments to minimize the number of users who can perform deletions. 2) Implement monitoring and alerting on bulk deletion operations, especially those involving PAM accounts, to detect suspicious activity promptly. 3) Enforce multi-factor authentication (MFA) for all users with delete permissions to reduce the risk of compromised credentials being used maliciously. 4) Until an official patch is released, consider implementing compensating controls such as disabling bulk deletion functionality or requiring additional confirmation steps for deletion of checked-out accounts. 5) Regularly back up PAM account configurations and credentials to enable rapid recovery in case of accidental or malicious deletions. 6) Engage with Devolutions support to obtain updates on patch availability and apply patches promptly once released. 7) Conduct periodic security training for administrators emphasizing the risks associated with improper deletion of privileged accounts and the importance of adhering to workflow controls.
Description
Improper Enforcement of Behavioral Controls in Devolutions Server 2025.3.15 and earlier allows an authenticated attacker with the delete permission to delete a PAM account that is currently checked out by selecting it alongside at least one non-checked-out account and performing a bulk deletion.