CVE-2026-9590
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 · uneditedImproper access control in the permission validation component in Devolutions Server 2026.1.19 and earlier allows an authenticated user with entry edit privileges to modify asset information without the required permission.
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 confidenceDevolutions Server contains an improper access control vulnerability in its permission validation component. An authenticated user with only entry edit privileges can bypass restrictions and modify asset information they should not have access to, due to insufficient permission checks in the affected component.
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< 2026.1.20.0CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Devolutions Server installationLocate the Devolutions Server installation directory or check installed programs on the system. Typically installed in C:\Program Files\Devolutions\Server or similar paths.Affected if Devolutions Server is installed on the system
-
Identify installed versionCheck the version of Devolutions Server through the application itself (usually in Help > About or the server management console), or check version information in the installation directory.Affected if The installed version is lower than 2026.1.20.0
-
Verify asset management feature is in useDetermine if the asset management module is enabled and being used. Check if users have access to asset creation or modification features within the Devolutions Server interface.Affected if Asset management functionality is enabled and accessible to users
-
Review user role assignmentsExamine user roles and permissions in the Devolutions Server administration panel. Look for users granted entry edit privileges or asset modification permissions.Affected if Users with entry edit privileges exist in the system who should not have asset modification capabilities
A user is affected if Devolutions Server version is below 2026.1.20.0 AND the asset management feature is enabled with users possessing entry edit privileges in an environment where permission boundaries are not properly enforced.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2026.1.20.0
Update Devolutions Server to version 2026.1.20 or later to remediate this vulnerability. Until the patch is applied, monitor for unauthorized asset modifications and review user privilege assignments to limit exposure.
Devolutions Server 2026.1.20.0
- Identify the current installed version of Devolutions Server by checking the About or Version section in the application
- Back up the Devolutions Server database and configuration files before upgrading
- Download Devolutions Server version 2026.1.20.0 or later from the official Devolutions download page
- Run the installer and follow the on-screen instructions to upgrade the installation
- After upgrade, verify the version is correctly showing 2026.1.20.0 or later
- Log in as an authenticated user with entry edit privileges and verify that the permission validation now correctly restricts modification of asset information beyond their authorized permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9590 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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