CVE-2026-12105
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 Devolutions Server 2026.2.5, 2026.1.21 allows an authenticated user to access attachments via folder duplication with inherited permissions.
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 allows an authenticated user to access attachments via folder duplication with inherited permissions. The vulnerability occurs because folder duplication does not correctly enforce access controls, allowing users to gain access to attachments in duplicated folders that they should not have permissions to view.
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.22.0>= 2026.2.4.0, < 2026.2.7.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.
-
Identify installed Devolutions Server versionLocate the installed version of Devolutions Server through the administration console, service information, or installation records. Compare the version number against the affected ranges: < 2026.1.22.0 or >= 2026.2.4.0 and < 2026.2.7.0Affected if The installed version falls within < 2026.1.22.0 or >= 2026.2.4.0 but < 2026.2.7.0
-
Determine if folder duplication has been usedReview the Devolutions Server environment for any folders that were duplicated, as this feature must be exercised for the access control flaw to be relevantAffected if Folder duplication has been performed on the server
-
Audit attachments in duplicated foldersExamine attachments stored within duplicated folders and review access logs to identify whether users who should not have permission were able to access these attachmentsAffected if Users accessed attachments in duplicated folders that they were not explicitly granted permission to view
The environment is affected if Devolutions Server version is below 2026.1.22.0 or between 2026.2.4.0 and 2026.2.6.x AND folder duplication has been performed, potentially allowing unauthorized access to attachments.
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.22.02026.2.7.0
Apply vendor security updates (2026.2.6 or later, 2026.1.22 or later) to Devolutions Server. After patching, audit folder permissions and access logs to confirm no unauthorized access occurred.
2026.1.22.0 (for 2026.1.x branch) or 2026.2.7.0 (for 2026.2.x branch)
- Identify the currently installed Devolutions Server version by checking the application or system information
- If running version < 2026.1.22.0, plan upgrade to version 2026.1.22.0 or later
- If running version >= 2026.2.4.0 and < 2026.2.7.0, plan upgrade to version 2026.2.7.0 or later
- Obtain the upgrade package from the official Devolutions download center at devolutions.net
- Follow standard Devolutions Server upgrade documentation for your deployment type
- After upgrade, verify the new version is installed correctly
- Test that the authorization controls function properly for attachment access via folder duplication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12105 — 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-12105 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