Devolutions Server up to 2025.3.20.0/2026.1.16.0 authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Devolutions Server up to 2025.3.20.0/2026.1.16.0. It has been rated as critical. This vulnerability affects unknown code. The manipulation leads to authorization. This vulnerability is referenced as CVE-2026-9248. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Devolutions Server up to 2025.3.20.0/2026.1.16.0 and classified as critical. This issue affects an unknown function. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Authorization bypass in the entry duplication feature in Devolutions Server allows an authenticated user with write access to any vault to copy documentation and attachments from an entry in a vault they cannot access via a crafted save request. This issue affects : * Devolutions Server 2026.1.6.0 through 2026.1.16.0 * Devolutions Server 2025.3.20.0 and earlier
The advisory is shared at devolutions.net. The identification of this vulnerability is CVE-2026-9248 since 05/21/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/22/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-31454). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 2025.3.0
- 2025.3.1
- 2025.3.2
- 2025.3.3
- 2025.3.4
- 2025.3.5
- 2025.3.6
- 2025.3.7
- 2025.3.8
- 2025.3.9
- 2025.3.10
- 2025.3.11
- 2025.3.12
- 2025.3.13
- 2025.3.14
- 2025.3.15
- 2025.3.16
- 2025.3.17
- 2025.3.18
- 2025.3.19
- 2025.3.20.0
- 2026.1.0
- 2026.1.1
- 2026.1.2
- 2026.1.3
- 2026.1.4
- 2026.1.5
- 2026.1.6
- 2026.1.7
- 2026.1.8
- 2026.1.9
- 2026.1.10
- 2026.1.11
- 2026.1.12
- 2026.1.13
- 2026.1.14
- 2026.1.15
- 2026.1.16.0
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/21/2026 CVE reserved05/22/2026 Advisory disclosed
05/22/2026 VulDB entry created
05/22/2026 VulDB entry last update
Sources
Advisory: DEVO-2026-0013Status: Confirmed
CVE: CVE-2026-9248 (🔒)
GCVE (CVE): GCVE-0-2026-9248
GCVE (VulDB): GCVE-100-365225
EUVD: 🔒
Entry
Created: 05/22/2026 18:07Updated: 05/22/2026 18:43
Changes: 05/22/2026 18:07 (52), 05/22/2026 18:43 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.