dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-4924

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 two-factor authentication (2FA) feature in Devolutions Server 2026.1.11 and earlier allows a remote attacker with valid credentials to bypass multifactor authentication and gain unauthorized access to the victim account via reuse of a partially authenticated session token.

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 2026.1.11 and earlier contains an improper authentication vulnerability in the 2FA feature. A remote attacker with valid credentials can bypass multifactor authentication by reusing a partially authenticated session token, allowing unauthorized access to the victim account without completing the second factor verification.

MitigationUpgrade to Devolutions Server version 2026.1.12 or later to remediate this vulnerability. After upgrading, verify that the 2FA authentication flow properly invalidates session tokens after each authentication step.

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 if Devolutions Server is installed
    Check for Devolutions Server installation in your environment using system inventory tools, Windows Programs and Features, or by locating the installation directory
    Affected if Devolutions Server is present on the system
  2. Determine the installed Devolutions Server version
    Launch Devolutions Server Manager and navigate to Help > About, or check the version listed in Windows Programs and Features
    Affected if The installed version falls within the affected ranges: < 2025.3.18.0 OR >= 2026.1.1.0 AND < 2026.1.12.0
  3. Verify if 2FA is enabled
    In the Devolutions Server administration console, go to User Management or Security Settings and check whether Two-Factor Authentication is configured and active for any accounts
    Affected if 2FA is enabled, making the authentication bypass vulnerability applicable to affected versions
  4. Inspect session token behavior during 2FA flow
    Review authentication logs or perform a test login while capturing network traffic to observe whether session tokens from a partially authenticated state (after first factor) remain valid and reusable
    Affected if Session tokens from incomplete 2FA attempts can be reused to gain full account access without completing the second factor

You are affected if Devolutions Server is installed with a version in the vulnerable range and 2FA is enabled, allowing a remote attacker with valid credentials to bypass the second authentication factor by reusing a partially authenticated session token.

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

Upgrade to Devolutions Server version 2026.1.12 or later to remediate this vulnerability. After upgrading, verify that the 2FA authentication flow properly invalidates session tokens after each authentication step.

Recommended fix High confidence

Upgrade to Devolutions Server 2026.1.12.0 or later (or 2025.3.18.0+ for older branch)

  1. 1. Identify the currently installed Devolutions Server version by checking the application or installation directory.
  2. 2. If running version 2026.1.1.0 through 2026.1.11.0, upgrade to version 2026.1.12.0 or later.
  3. 3. If running version older than 2025.3.18.0, upgrade to version 2025.3.18.0 or later.
  4. 4. After upgrading, verify that the 2FA authentication flow works correctly and that session tokens are properly invalidated after partial authentication.
  5. 5. Review audit logs to confirm no unauthorized access occurred during the vulnerability window.
Caveat Review release notes for any configuration or behavior changes between versions

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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