Skip to main content
VulnerabilityPublished

CVE-2026-4829: Devolutions Server · Improper Authentication

Affects Devolutions ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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-4829, organizations should implement the following specific measures: 1) Monitor Devolutions Server environments for unusual authentication patterns, especially reuse of OAuth session codes or unexpected privilege escalations. 2) Restrict OAuth session code lifetimes and enforce strict single-use policies to prevent reuse. 3) Apply principle of least privilege to limit the number of users with administrative rights, reducing the impact of potential impersonation. 4) Implement multi-factor authentication (MFA) on all accounts, particularly administrators, to add an additional layer of security beyond OAuth tokens. 5) Once a patch or update is released by Devolutions, prioritize immediate deployment to remediate the vulnerability. 6) Review and harden OAuth integration configurations, ensuring tokens and session codes are securely validated and invalidated after use. 7) Conduct regular security audits and penetration tests focusing on authentication flows to detect similar weaknesses. 8) Educate users about the risks of session reuse and ensure secure session management practices are followed. These steps go beyond generic advice by focusing on OAuth session code management and administrative privilege controls specific to this vulnerability.

Description

Improper authentication in the external OAuth authentication flow in Devolutions Server 2026.1.11 and earlier allows an authenticated user to authenticate as other users, including administrators, via reuse of a session code from an external authentication flow.

References

Community reviews

Loading reviews…