Skip to main content
CVE-2025-8312VulnerabilityPublished Updated

CVE-2025-8312: Devolutions Server · Deadlock

Affects Devolutions ServerSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Devolutions ServerAffected
  • =2025.2.2.0
  • =0
Fixed in–

AI-suggested

Beyond applying vendor patches once available, European organizations should implement several specific mitigations: 1) Temporarily disable or restrict the PAM automatic check-in feature if feasible, to prevent reliance on the scheduling service that may deadlock. 2) Enforce strict manual monitoring and auditing of privileged credential check-outs and check-ins to detect anomalies or extended usage periods. 3) Implement compensating controls such as multi-factor authentication (MFA) on privileged accounts to reduce risk from prolonged password validity. 4) Use network segmentation and least privilege principles to limit the impact of compromised credentials. 5) Monitor logs and system behavior for signs of deadlock conditions or scheduling service failures, enabling rapid incident response. 6) Conduct regular reviews of privileged access policies and ensure that password expiration and rotation policies are enforced through alternative mechanisms if the automatic check-in is unreliable. 7) Prepare incident response plans specifically addressing scenarios of prolonged privileged access and potential service disruptions caused by deadlocks. These targeted actions will help mitigate the risk until a patch is deployed and fully tested.

Description

Deadlock in PAM automatic check-in feature in Devolutions Server allows a password to remain valid beyond the end of its intended check-out period due to a deadlock occurring in the scheduling service.This issue affects the following version(s) : * Devolutions Server 2025.2.2.0 through 2025.2.5.0 * Devolutions Server 2025.1.12.0 and earlier

References

Community reviews

Loading reviews…