CVE-2026-5175
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceImproper access control in Devolutions Server's MFA management API allows authenticated attackers to delete their own configured MFA factors through crafted HTTP requests, reducing account protection to password-only authentication. This affects versions 2026.1.6 through 2026.1.11.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2026.1.6.0, < 2026.1.12.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Devolutions Server versionCheck the installed version of Devolutions Server. This is typically visible in the Server Manager console, or by examining the application binaries or installation metadata on the server. Compare the version number against the affected range: 2026.1.6.0 through 2026.1.11.x.Affected if The installed version is 2026.1.6.0 or higher but lower than 2026.1.12.0
-
Verify MFA is configured on any user accountsReview user account configurations in Devolutions Server to determine if any accounts have MFA factors (such as TOTP, push notification, or other MFA methods) enabled. This can be done through the Server Manager administrative interface by examining user security settings.Affected if Any user accounts in the system have MFA factors configured, making them potential targets for this vulnerability
-
Review authentication audit logs for MFA deletion eventsExamine Devolutions Server audit logs or security event logs for recent events indicating MFA factor deletion or removal. Look for API calls or operations that removed MFA from user accounts, particularly if performed by the account owner.Affected if Audit logs show unexpected or unauthorized MFA factor deletions where users removed their own MFA methods
A user is affected if their Devolutions Server installation is version 2026.1.6.0 through 2026.1.11.x and has user accounts with MFA configured, since an authenticated attacker could delete their own MFA factors via the vulnerable API endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.1.12.0
Upgrade Devolutions Server to version 2026.1.12 or later where the patch is applied, and audit user accounts for unexpected MFA configuration changes.
2026.1.12.0
- Identify all instances of Devolutions Server running version 2026.1.6.0 through 2026.1.11
- Schedule a maintenance window for the upgrade
- Back up the Devolutions Server database and configuration
- Download Devolutions Server version 2026.1.12.0 or later from the official Devolutions download portal
- Follow the standard Devolutions Server upgrade documentation to apply the update
- Verify the upgrade was successful by checking the Server version
- Confirm MFA functionality is working correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5175 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5175 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data