dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-4829

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 2026.1.12.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an authentication bypass vulnerability in Devolutions Server's external OAuth flow. An authenticated attacker can reuse a session code from an OAuth authentication flow to impersonate other users, including administrators, effectively hijacking or forging sessions for privileged accounts.

MitigationUpgrade to Devolutions Server version 2026.1.12 or later, which contains the fix for proper session code validation in the OAuth authentication flow. If immediate patching is not possible, consider restricting external OAuth authentication or implementing additional monitoring for suspicious authentication patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Devolutions ServerApplication
Affected:< 2026.1.12.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Devolutions Server is installed
    Check for Devolutions Server installation on the system. This may be visible in installed programs (Windows), package lists (Linux), or by querying the application's service status.
    Affected if Devolutions Server is not found on the system
  2. Determine the installed Devolutions Server version
    Access the Devolutions Server admin console or use the product's built-in version check mechanism to identify the currently installed version number.
    Affected if The installed version is earlier than 2026.1.12.0
  3. Check if external OAuth authentication is configured
    Review the Devolutions Server authentication settings to determine if any external OAuth providers (such as Azure AD, Okta, Google, etc.) are enabled for user authentication.
    Affected if External OAuth authentication providers are configured and enabled
  4. Audit authentication logs for session code anomalies
    Review Devolutions Server authentication and audit logs for instances where session codes from OAuth flows may have been reused or where session hijacking patterns are observable.
    Affected if Suspicious session code reuse patterns are found in authentication logs

The environment is affected if Devolutions Server is installed with a version lower than 2026.1.12.0 and external OAuth authentication is enabled, allowing an authenticated attacker to potentially reuse OAuth session codes to impersonate other users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.1.12.0 or later
Fixed in 2026.1.12.0
Interim mitigation

Upgrade to Devolutions Server version 2026.1.12 or later, which contains the fix for proper session code validation in the OAuth authentication flow. If immediate patching is not possible, consider restricting external OAuth authentication or implementing additional monitoring for suspicious authentication patterns.

Recommended fix High confidence

2026.1.12.0

  1. Back up the current Devolutions Server installation and database before upgrading
  2. Download Devolutions Server version 2026.1.12.0 or later from the official Devolutions download center (devolutions.net)
  3. Stop the Devolutions Server service
  4. Install the updated version using the standard upgrade procedure
  5. Restart the Devolutions Server service
  6. Verify the upgrade was successful by checking the version number in the administration console
  7. Test that external OAuth authentication no longer allows session code reuse between users

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4829 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4829 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data