CVE-2026-3131
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 multiple DVLS REST API endpoints in Devolutions Server 2025.3.14.0 and earlier allows an authenticated user with view-only permission to access sensitive connection data.
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 · moderate confidenceImproper access control in Devolutions Server DVLS REST API endpoints allows authenticated users with view-only permission to bypass authorization and access sensitive connection data that should be restricted. This is a privilege escalation/authorization bypass issue affecting version 2025.3.14.0 and earlier.
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< 2025.3.15.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Check Devolutions Server installed versionLocate the Devolutions Server installation and check the version number (typically found in the product UI under About/Help, or in installation directories). Compare it to the affected range: versions earlier than 2025.3.15.0 are vulnerable.Affected if Installed version is 2025.3.14.0 or earlier
-
Verify REST API is enabledCheck the Devolutions Server configuration or management interface to confirm the DVLS REST API endpoints are enabled and accessible.Affected if REST API endpoints are enabled and exposed
-
Identify view-only user accountsReview user accounts and their assigned permissions in the Devolutions Server management console. Look for accounts that have only view-only or read-only permission levels.Affected if There are user accounts with view-only permissions in the system
-
Check for sensitive connection data exposureUsing a view-only account, attempt to access REST API endpoints for connection data (such as /api/connections, /api/credentials, or similar endpoints that should require higher privileges).Affected if View-only accounts can retrieve sensitive connection or credential data via the API that should be restricted
A user is affected if they run Devolutions Server version 2025.3.14.0 or earlier with the REST API enabled and have view-only users in the system who can access restricted connection data.
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 · scoped2025.3.15.0
Update Devolutions Server to version 2025.3.14.0 or later to patch the improper access control in the DVLS REST API endpoints. If immediate patching is not feasible, review and audit user permission assignments to minimize exposure.
2025.3.15.0 or later
- Upgrade Devolutions Server to version 2025.3.15.0 or later to remediate the improper access control vulnerability
- After upgrade, verify that view-only users can no longer access sensitive connection data through the DVLS REST API endpoints
- Consult Devolutions Server 2025.3.15.0 release notes for any configuration or migration requirements
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3131 — 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-3131 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