dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-4927

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 2026.1.12.0 or later.
See remediation →
71/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
Exposure of sensitive information in the users MFA feature in Devolutions Server allows users with user management privileges to obtain other users OTP keys via an authenticated API 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 · high confidence

Authenticated users with user management privileges can invoke an API endpoint to retrieve other users' OTP (One-Time Password) secret keys used for multi-factor authentication. This exposes sensitive MFA credentials belonging to other users through an improperly authorized API response.

MitigationDevolutions should restrict API access to OTP keys by implementing proper authorization checks and filtering sensitive MFA data from API responses. Users may want to rotate their MFA credentials as a precautionary measure until the patch is applied.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Confirm Devolutions Server installation
    Locate Devolutions Server installation directory or check system services for 'Devolutions Server' process
    Affected if Devolutions Server is installed on the system
  2. Identify installed version
    Check the installed version through the server administration interface, installed programs list, or version file in the installation directory
    Affected if Installed version falls within >= 2026.1.6.0 and < 2026.1.12.0
  3. Verify user management privileges exist
    Check if any user accounts have been assigned user management or administrative privileges within the Devolutions Server user management module
    Affected if Multiple user accounts with elevated privileges exist in the system
  4. Check API authorization for OTP data
    Using an account with user management privileges, attempt to access the user API endpoint that returns user details and inspect whether OTP secret keys are included in the response
    Affected if API responses expose OTP secret keys for users other than the authenticated requester

Users are affected if they run Devolutions Server version 2026.1.6.0 through 2026.1.11.x and have accounts with user management privileges enabled, as the API improperly returns OTP secrets for 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

Devolutions should restrict API access to OTP keys by implementing proper authorization checks and filtering sensitive MFA data from API responses. Users may want to rotate their MFA credentials as a precautionary measure until the patch is applied.

Recommended fix High confidence

2026.1.12.0

  1. 1. Back up the current Devolutions Server database and configuration files before upgrading.
  2. 2. Download Devolutions Server version 2026.1.12.0 or later from the official Devolutions website (https://devolutions.net/server).
  3. 3. Stop the Devolutions Server service to prevent active connections during the upgrade.
  4. 4. Run the installer for version 2026.1.12.0, following the on-screen prompts to complete the upgrade.
  5. 5. Start the Devolutions Server service after the upgrade completes.
  6. 6. Verify the MFA feature now properly restricts OTP key access - users with user management privileges should no longer be able to retrieve other users OTP keys via API requests.
  7. 7. Test that legitimate MFA functionality remains operational 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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