VulnerabilityPublished 24 Feb 2026Updated 26 Feb 2026

CVE-2026-3131: Devolutions Server · Information Exposure

Affects Devolutions ServerSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2025.3.15 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.3.15

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Devolutions Server to 2025.3.15.

Affected software

Product	Affected	Fixed in
DevolutionsServer	Affected <2025.3.15	Fixed in 2025.3.15

AI-suggested

1. 2. If you cannot patch yet, restrict access to the Devolutions Server REST API to trusted and minimal user groups, ensuring that only necessary personnel have authenticated access. 3. Review and tighten role-based access controls (RBAC) to ensure that view-only users cannot access sensitive connection data beyond their permissions. 4. Implement network segmentation and firewall rules to limit exposure of the Devolutions Server API endpoints to internal networks or trusted IP addresses only. 5. Enable detailed logging and monitoring of API access to detect any unusual or unauthorized attempts to access sensitive data. 6. Conduct regular audits of user permissions and API usage to identify and remediate any privilege creep or misconfigurations. 7. Educate administrators and users about the risks of exposing sensitive connection data and enforce strong authentication mechanisms to reduce the risk of compromised credentials. 8. Consider deploying additional security controls such as Web Application Firewalls (WAF) to detect and block suspicious API requests targeting sensitive endpoints.

Description

Improper 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.

Impact

The primary impact of CVE-2026-3131 is the unauthorized disclosure of sensitive connection data to users who should only have view-only access. This exposure can compromise confidentiality by revealing credentials, connection parameters, or other sensitive configuration details. Attackers or malicious insiders exploiting this vulnerability could leverage the disclosed information to escalate privileges, move laterally within networks, or access critical systems. Although the vulnerability does not affect data integrity or availability directly, the confidentiality breach can lead to significant downstream security incidents, including data breaches or operational disruptions. Organizations using Devolutions Server for managing privileged access are particularly at risk, as the exposed data could undermine the security of remote access infrastructure. The ease of exploitation and remote accessibility increase the likelihood of exploitation once the vulnerability becomes widely known or if attackers gain authenticated access. Overall, this vulnerability poses a moderate risk that could have serious consequences if combined with other attack vectors.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

devolutions.net/security/advisories/DEVO-2026-0004/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Mar 2026, 20:13 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats