dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-9251

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-22
Fix available
A fix is available. Upgrade to 2025.3.22.0 / 2026.1.19.0 or later.
See remediation →
60/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
Missing authorization in the entry status management feature in Devolutions Server allows a non-administrator authenticated user to bypass the administrator-enforced Pending Approval flow and gain access to an entry's data via a crafted status change request. This issue affects : * Devolutions Server 2026.1.6.0 through 2026.1.16.0 * Devolutions Server 2025.3.20.0 and earlier

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

Missing authorization check in Devolutions Server's entry status management allows authenticated non-administrator users to craft status change requests that bypass the administrator-enforced Pending Approval workflow, enabling unauthorized access to entry data.

MitigationApply vendor-supplied patch or upgrade to a version beyond 2026.1.16.0 (for 2026.x) or beyond 2025.3.20.0 (for 2025.x) that includes proper authorization validation for the status management feature.

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.22.0>= 2026.1.6.0, < 2026.1.19.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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 installed Devolutions Server version
    Access the Devolutions Server administration console or check the product's About/Version information page. Locate the exact version number displayed in the server management interface.
    Affected if The installed version is either below 2025.3.22.0, or falls between 2026.1.6.0 and 2026.1.19.0 (inclusive of the lower bound, exclusive of the upper bound).
  2. Verify Pending Approval workflow is configured
    Navigate to the entry management or approval workflow settings within the Devolutions Server administration panel. Check whether any entries or entry templates have the Pending Approval status workflow enabled.
    Affected if The Pending Approval workflow feature is actively configured for at least one entry or entry type in the system.
  3. Confirm presence of non-administrator users with entry access
    Review user management and role assignments. Identify users assigned to roles other than Administrator who have access to view or manage entries.
    Affected if There are authenticated users with non-administrator roles who have permissions to access entry data.
  4. Inspect entry status change permissions
    Examine the role-based access control (RBAC) or permission settings for non-administrator roles. Specifically review whether these roles allow direct status modification on entries without approval workflow enforcement.
    Affected if Non-administrator roles possess permissions to change entry status bypassing the configured approval workflow controls.

Your environment is affected if you run a vulnerable Devolutions Server version AND have the Pending Approval workflow configured with non-administrator users who can potentially bypass status enforcement.

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.22.0 / 2026.1.19.0 or later
Fixed in 2025.3.22.02026.1.19.0
Interim mitigation

Apply vendor-supplied patch or upgrade to a version beyond 2026.1.16.0 (for 2026.x) or beyond 2025.3.20.0 (for 2025.x) that includes proper authorization validation for the status management feature.

Recommended fix High confidence

Devolutions Server 2025.3.22.0 or later for the 2025.x branch; Devolutions Server 2026.1.19.0 or later for the 2026.x branch

  1. Identify the currently installed Devolutions Server version by checking the application or system information
  2. For versions 2025.3.20.0 and earlier: Upgrade to Devolutions Server 2025.3.22.0 or later
  3. For versions 2026.1.6.0 through 2026.1.16.0: Upgrade to Devolutions Server 2026.1.19.0 or later
  4. After upgrading, verify that the entry status management feature now properly enforces authorization checks
  5. Confirm that non-administrator users can no longer bypass the Pending Approval flow through crafted status change requests
Caveat Review release notes for any configuration or behavioral changes between your current version and the target version

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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