dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-4925

MEDIUM · 5.0 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 2026.1.12.0 or later.
See remediation →
56/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 access control in the users MFA feature in Devolutions Server allows an authenticated user to bypass administrator-enforced restrictions and remove their own multi-factor authentication (MFA) configuration via a crafted request. This issue affects Server: from 2026.1.6 through 2026.1.11.

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

Improper access control in Devolutions Server's MFA feature allows authenticated users to bypass administrator-enforced MFA requirements and remove their own MFA configuration through a crafted request. This is a client-side enforcement vulnerability where server-side validation of admin policies is missing, enabling users to circumvent security controls intended to be mandatory.

MitigationUpdate to Devolutions Server version beyond 2026.1.11 when a patch is available, and verify that server-side enforcement properly rejects attempts to disable MFA when an administrator has mandated its use.

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.6.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
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/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 Devolutions Server installation and version
    Locate the Devolutions Server installation and determine its exact version number. This is typically found in the application itself, or via the program's properties/details in the installation directory.
    Affected if The installed version falls within >= 2026.1.6.0 and < 2026.1.12.0
  2. Confirm MFA feature is configured
    Verify whether the MFA (Multi-Factor Authentication) feature is enabled and configured for user accounts in the Devolutions Server environment.
    Affected if MFA is configured and the server version is in the affected range; the vulnerability requires MFA to be present to exploit
  3. Check for administrator-enforced MFA policies
    Review the server's administrative settings to determine if there are policies mandating MFA for users, which is the specific security control this vulnerability allows bypassing.
    Affected if Admin MFA enforcement policies exist and the server version is vulnerable; the flaw specifically allows circumvention of mandatory MFA requirements
  4. Verify server-side validation of MFA changes
    If admin MFA enforcement is configured, test whether the server properly rejects attempts by users to disable MFA or remove their MFA configuration when an administrator has mandated its use.
    Affected if Server accepts user requests to remove/disable MFA even when admin policy requires it to be mandatory - this indicates the vulnerability is present

A system is affected if it runs Devolutions Server version 2026.1.6.0 through 2026.1.11.x and has MFA configured with administrator-enforced requirements that can be circumvented by user requests.

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

Update to Devolutions Server version beyond 2026.1.11 when a patch is available, and verify that server-side enforcement properly rejects attempts to disable MFA when an administrator has mandated its use.

Recommended fix High confidence

2026.1.12.0 or later

  1. Backup the current Devolutions Server installation and database before proceeding with the upgrade
  2. Upgrade Devolutions Server to version 2026.1.12.0 or later to address the missing authorization vulnerability
  3. After upgrade, verify the MFA configuration functions correctly
  4. Confirm that administrator-enforced MFA restrictions are properly enforced for all users

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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