dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-3224

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-03
Fix available
A fix is available. Upgrade to 2025.3.16.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Authentication bypass in the Microsoft Entra ID (Azure AD) authentication mode in Devolutions Server 2025.3.15.0 and earlier allows an unauthenticated user to authenticate as an arbitrary Entra ID user via a forged JSON Web Token (JWT).

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 2025.3.15.0 and earlier contain an authentication bypass in the Microsoft Entra ID (Azure AD) authentication mode that allows unauthenticated attackers to impersonate any Entra ID user by submitting a forged JWT token during the authentication flow.

MitigationUpgrade Devolutions Server to a version newer than 2025.3.15.0 that addresses this vulnerability. Until patched, consider temporarily disabling Entra ID authentication or implementing additional monitoring for anomalous JWT-based authentication attempts.

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.16.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 directory and check the version. Common paths include C:\Program Files\Devolutions\Server\ or check the application via Windows Programs and Features. The version is typically displayed in the application or can be found in an About section.
    Affected if The installed version is lower than 2025.3.16.0 (e.g., 2025.3.15.0, 2025.2.x, etc.)
  2. Confirm Entra ID authentication is enabled
    Access the Devolutions Server administration console and navigate to Authentication settings. Look for Microsoft Entra ID (formerly Azure AD) authentication configuration. This is typically found under Configuration > Authentication > Entra ID.
    Affected if Entra ID authentication method is actively configured and enabled for user logins
  3. Check JWT token configuration for Entra ID
    Review the Entra ID integration settings in Devolutions Server. Examine the token validation and signing key configuration to verify if default or insecure settings are in use. This is usually accessible via the authentication provider settings in the admin panel.
    Affected if Entra ID is enabled with default JWT configuration without custom token validation safeguards

You are affected if Devolutions Server version is below 2025.3.16.0 AND Entra ID authentication is enabled in your environment.

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.16.0 or later
Fixed in 2025.3.16.0
Interim mitigation

Upgrade Devolutions Server to a version newer than 2025.3.15.0 that addresses this vulnerability. Until patched, consider temporarily disabling Entra ID authentication or implementing additional monitoring for anomalous JWT-based authentication attempts.

Recommended fix High confidence

2025.3.16.0

  1. 1. Back up your current Devolutions Server installation and database before proceeding with the upgrade.
  2. 2. Download Devolutions Server version 2025.3.16.0 or later from the official Devolutions website (devolutions.net).
  3. 3. Install or update to the downloaded version following the standard upgrade procedure.
  4. 4. After installation, verify that the Microsoft Entra ID (Azure AD) authentication is functioning correctly.
  5. 5. Confirm the version number in the application to ensure the patch was applied successfully.

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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