Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 5

How to Fix CVE-2026-5175: Server (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

⚡ At a glance
SeverityCVSS 5, Medium
Actively exploited?No
AffectedDevolutions Server (2026.1.6 <= 2026.1.11)
Fixed inSame patched build as CVE-2026-4828
Type (CWE)CWE-862

CVE-2026-5175 is a sibling vulnerability in the same Devolutions Server advisory bundle as CVE-2026-4828. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-5175 matches the primary write-up.

What is different about CVE-2026-5175?

Improper access control in the multi-factor authentication (MFA) management API in Devolutions Server allows an authenticated attacker to delete their own configured MFA factors and reduce account protection to password-only authentication via crafted HTTP requests. This issue affects Server: from 2026.1.6 through 2026.1.11.

Impact is consistent with the bundle: compromise of the affected component as described in the vendor advisory. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-5175

Apply the patched build per the primary write-up: How to Fix CVE-2026-4828.

For a quick check, confirm the running version of Server:


# Confirm the installed version via your package manager
dpkg -l | grep -i server   # Debian/Ubuntu
rpm -qa | grep -i server   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-5175 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-5175?

CVSS rates it 5 (Medium). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take Server offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-5175 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References


*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Devolutions Server advisory bundle. Full procedure at how-to-fix-cve-2026-4828.*