Skip to main content
VulnerabilityPublished

CVE-2026-4924: Devolutions Server · CWE-1390

Affects Devolutions ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% 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:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Apr 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

Affected software

ProductAffectedFixed in
DevolutionsServerAffected
  • <=2026.1.11
Fixed in–

AI-suggested

To mitigate CVE-2026-4924, organizations should implement the following specific measures: 1) Immediately review and restrict access to Devolutions Server accounts, ensuring that only necessary personnel have valid credentials. 2) Monitor authentication logs for unusual session token reuse or anomalies indicating partial authentication token exploitation. 3) Enforce strong password policies and consider additional layers of authentication outside of the vulnerable 2FA mechanism, such as network-level access controls or VPNs. 4) Isolate Devolutions Server instances within secure network segments to limit exposure. 5) Engage with Devolutions for updates and patches addressing this vulnerability and plan for rapid deployment once available. 6) Conduct internal penetration testing focusing on session management and 2FA bypass attempts to identify potential exploitation. 7) Educate users about the importance of credential security and the risks of credential reuse across systems. 8) Consider implementing compensating controls such as session token expiration policies and multi-layered authentication to reduce the window of opportunity for token reuse attacks. These steps go beyond generic advice by focusing on session token monitoring, network segmentation, and proactive engagement with the vendor.

Description

Improper authentication in the two-factor authentication (2FA) feature in Devolutions Server 2026.1.11 and earlier allows a remote attacker with valid credentials to bypass multifactor authentication and gain unauthorized access to the victim account via reuse of a partially authenticated session token.

References

Community reviews

Loading reviews…