CVE-2026-15641
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 authorization in the access request status endpoint in Devolutions Server 2026.2.11, 2026.1.22 allows an authenticated low-privileged user to approve their own pending access request via a direct call to the request status endpoint, bypassing the required approver review.
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 confidenceImproper authorization in the access request status endpoint of Devolutions Server 2026.1.22 and 2026.2.11 allows an authenticated low-privileged user to approve their own pending access request by directly calling the status endpoint, bypassing the mandatory approver review process.
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.23.0>= 2026.2.0.0, < 2026.2.12.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Identify installed Devolutions Server versionAccess the server administration interface or check the product documentation for the installed version number. This is typically found in the About or System Information section of the management console.Affected if The version falls within >= 2026.1.1 and < 2026.1.23.0, or >= 2026.2.4.0 and < 2026.2.12.0
-
Verify access request module is configuredCheck if the Access Request feature is enabled in Devolutions Server. This feature allows users to request elevated access to resources and requires approver review. Inspect the system configuration or audit logs for any access request-related activity.Affected if The access request feature is enabled and in use on the server
-
Check for low-privileged authenticated usersReview user accounts and their permission levels in the Devolutions Server user management console. Identify whether there are authenticated users who do not have approver privileges.Affected if There are authenticated low-privileged users without approver rights who have access to the access request functionality
-
Inspect access request audit logsExamine the audit or activity logs for access request status changes. Look for any status modifications that were performed directly on the status endpoint rather than through the proper approver workflow.Affected if Audit logs show access request status changes performed by non-approver users bypassing the normal approval workflow
The environment is affected if Devolutions Server version is within the vulnerable ranges AND the access request feature is enabled with low-privileged users present who could bypass the approver review process.
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.23.02026.2.12.0
Apply the vendor patch for Devolutions Server that implements proper authorization checks on the access request status endpoint, ensuring only users with approver privileges can modify request status.
Upgrade to Devolutions Server 2026.1.23.0 or later for 2026.1.x users; upgrade to 2026.2.12.0 or later for 2026.2.x users
- 1. Identify the currently installed Devolutions Server version using the Server Manager or About section
- 2. If running 2026.1.x branch (version >= 2026.1.1 and < 2026.1.23.0): Plan upgrade to version 2026.1.23.0 or later
- 3. If running 2026.2.x branch (version >= 2026.2.4.0 and < 2026.2.12.0): Plan upgrade to version 2026.2.12.0 or later
- 4. Review Devolutions Server release notes for the target version for any prerequisites
- 5. Perform a complete backup of the Devolutions Server database before upgrading
- 6. Download the installer for the target fixed version from the official Devolutions downloads page
- 7. Execute the installer and follow the on-screen upgrade wizard instructions
- 8. After upgrade, verify the Server version reflects the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15641 — 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-15641 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