Devolutions Server up to 2025.3.17/2026.1.11 API server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.08 |
Summary
A vulnerability, which was classified as critical, has been found in Devolutions Server up to 2025.3.17/2026.1.11. The impacted element is an unknown function of the component API Handler. This manipulation causes server-side request forgery. This vulnerability is handled as CVE-2026-4989. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical was found in Devolutions Server up to 2025.3.17/2026.1.11. Affected by this vulnerability is an unknown functionality of the component API Handler. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Improper input validation in the gateway health check feature in Devolutions Server allows a low-privileged authenticated user to perform server-side request forgery (SSRF), potentially leading to information disclosure, via a crafted API request. This issue affects Server: from 2026.1.1 through 2026.1.11, from 2025.3.1 through 2025.3.17.
It is possible to read the advisory at devolutions.net. This vulnerability is known as CVE-2026-4989 since 03/27/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/01/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for 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
- 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
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: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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
03/27/2026 CVE reserved04/01/2026 Advisory disclosed
04/01/2026 VulDB entry created
04/01/2026 VulDB entry last update
Sources
Advisory: DEVO-2026-0010Status: Confirmed
CVE: CVE-2026-4989 (🔒)
GCVE (CVE): GCVE-0-2026-4989
GCVE (VulDB): GCVE-100-354691
Entry
Created: 04/01/2026 17:51Changes: 04/01/2026 17:51 (54)
Complete: 🔍
Cache ID: 216:CF3:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.