dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-4828

HIGH · 8.2 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 2025.3.18.0 / 2026.1.12.0 or later.
See remediation →
88/100
Remediation priority · High
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 OAuth login functionality in Devolutions Server 2026.1.11 and earlier allows a remote attacker with valid credentials to bypass multi-factor authentication via a crafted login request.

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 · high confidence

Devolutions Server versions 2026.1.11 and earlier contain an improper authentication vulnerability in the OAuth login flow. An attacker with valid user credentials can send a crafted login request to bypass multi-factor authentication enforcement and gain unauthorized access to accounts that should require MFA.

MitigationApply vendor-supplied patch by upgrading Devolutions Server to version 2026.1.12 or later. After patching, verify that MFA enforcement is functioning correctly in the OAuth authentication flow.

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:< 2025.3.18.0>= 2026.1.1.0, < 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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/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 the installed Devolutions Server version
    Locate the Devolutions Server installation and retrieve its version number, typically found in the application metadata, About page, or installation directory.
    Affected if The installed version is either before 2025.3.18.0 OR falls between 2026.1.1.0 (inclusive) and 2026.1.12.0 (exclusive).
  2. Confirm OAuth login is configured
    Examine the Devolutions Server authentication settings to determine whether OAuth/OIDC-based authentication is enabled for user logins.
    Affected if OAuth authentication is active and users can log in via OAuth/OIDC flow.
  3. Verify MFA enforcement status
    Review the MFA (Multi-Factor Authentication) configuration in Devolutions Server, specifically checking whether MFA is mandated for all users or for OAuth-based logins.
    Affected if MFA is not enforced or can be bypassed for OAuth login sessions.

You are affected if Devolutions Server version falls within the vulnerable ranges AND OAuth login is enabled, allowing an attacker with valid credentials to bypass MFA verification.

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 2025.3.18.0 / 2026.1.12.0 or later
Fixed in 2025.3.18.02026.1.12.0
Interim mitigation

Apply vendor-supplied patch by upgrading Devolutions Server to version 2026.1.12 or later. After patching, verify that MFA enforcement is functioning correctly in the OAuth authentication flow.

Recommended fix High confidence

2025.3.18.0 (for 2025.x branch) or 2026.1.12.0 (for 2026.x branch)

  1. 1. Identify the current Devolutions Server version by checking the About or System Information page in the administration console, or running 'dvls --version' if using CLI
  2. 2. If the current version is < 2025.3.18.0 (2025.x branch), plan to upgrade to version 2025.3.18.0 or later
  3. 3. If the current version is >= 2026.1.1.0 and < 2026.1.12.0 (2026.x branch), plan to upgrade to version 2026.1.12.0 or later
  4. 4. Before upgrading, review Devolutions Server release notes for the target version and perform a backup of the database and configuration
  5. 5. Download the installer for the fixed version from the official Devolutions downloads page (devolutions.net)
  6. 6. Apply the upgrade following standard Devolutions Server upgrade procedures
  7. 7. After upgrade, verify that OAuth login with MFA is functioning correctly
  8. 8. Confirm the version has been updated successfully
Caveat Review release notes for any configuration changes or breaking changes between your current version and the target fixed version before upgrading

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4828 — 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-4828 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