Skip to main content
VulnerabilityPublished Updated

CVE-2026-1768: Devolutions Server · Incorrect Authorization

Affects Devolutions ServerSource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% 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:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade Devolutions Server to 2025.3.15.

Affected software

ProductAffectedFixed in
DevolutionsDevolutions ServerAffected
  • <2025.3.15
Fixed in
  • 2025.3.15

AI-suggested

To mitigate CVE-2026-1768, organizations should promptly upgrade Devolutions Server to version 2025.3.15 or later where the vulnerability is fixed. If immediate patching is not feasible, administrators should restrict access to the server to trusted networks and enforce strong authentication mechanisms to limit the pool of authenticated users. Implementing strict role-based access controls (RBAC) and regularly auditing user permissions can reduce the risk of privilege abuse. Monitoring logs for unusual access patterns or permission changes may help detect exploitation attempts. Additionally, isolating Devolutions Server from general user networks and employing network segmentation can limit exposure. Organizations should also consider temporary compensating controls such as disabling caching features if configurable, or applying custom access filters to prevent permission cache poisoning. Finally, educating users about credential security and promptly revoking access for compromised accounts will further reduce risk.

Description

A permission cache poisoning vulnerability in Devolutions Server allows authenticated users to bypass permissions to access entries.This issue affects Devolutions Server: before 2025.3.15.

References

Community reviews

Loading reviews…