LiveActive security incident?Get immediate response
CVE Record

CVE-2026-3131: Improper access control in multiple DVLS REST API endpoints in Devolutions Server 2025.3.14.0 and earlier...

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Devolutions Server versions 2025.3.14.0 and earlier have an access-control flaw in multiple DVLS REST API endpoints. A user who should only view limited content may access sensitive connection data. This is primarily a confidentiality risk for organizations relying on DVLS to protect privileged connection information.

Executive priority

Treat as a timely confidentiality issue, especially if DVLS stores privileged or sensitive connection records. Prioritize inventory, vendor guidance review, and patch planning. Escalate if many low-privilege users have access or if DVLS is reachable from broad internal networks.

Technical view

CVE-2026-3131 is a CWE-200 issue affecting Devolutions Server 2025.3.14.0 and earlier. The CVSS 3.1 score is 6.5: network-accessible, low complexity, low privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact stated.

Likely exposure

Exposure is limited to environments running affected Devolutions Server versions where authenticated users have view-only permissions and network access to DVLS REST API endpoints.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Abuse requires an authenticated account with low privileges. The main business concern is unintended disclosure of sensitive connection data, which may support later intrusion if credentials or connection details are exposed.

Researcher notes

The bundle identifies multiple affected REST API endpoints but does not name them or provide a fixed version. Do not assume exploit availability. The affected-version metadata appears sparse, so rely on the description stating Devolutions Server 2025.3.14.0 and earlier.

Mitigation direction

  • Identify Devolutions Server instances and confirm whether they are 2025.3.14.0 or earlier.
  • Review Devolutions advisory DEVO-2026-0004 for fixed versions or vendor-prescribed mitigations.
  • Update affected systems if a vendor-supported fixed release is available.
  • Restrict DVLS REST API access to trusted networks where feasible.
  • Review and minimize view-only user access until remediation is complete.

Validation and detection

  • Inventory DVLS versions across production, test, and backup environments.
  • Confirm whether any instance is 2025.3.14.0 or earlier.
  • Review user accounts with view-only permissions.
  • Check logs for unusual access to connection data by low-privilege users.
  • Track remediation against the vendor advisory and CVE record.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-3131 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-3131Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
DevolutionsServer0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.