CVE-2026-9047
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 handling of factor key state in the multi-factor authentication management feature in Devolutions Server allows an attacker with knowledge of a user's password to bypass the user's multi-factor authentication after the user reconfigures their factors. This issue affects : * Devolutions Server 2026.1.6.0 through 2026.1.16.0
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 · moderate confidenceA logic vulnerability in Devolutions Server's multi-factor authentication management allows an authenticated attacker with knowledge of a user's password to bypass MFA protections. The issue stems from improper handling of the factor key state after a user reconfigures their MFA factors, creating a window where authentication succeeds without completing MFA validation.
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.19.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
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.
-
Determine Devolutions Server installed versionLocate the version information through the product's administration console, installation directory, or system registry (typically under HKEY_LOCAL_MACHINE\SOFTWARE\Devolutions\Server or similar). Compare the installed version number against the affected range: 2026.1.6.0 through 2026.1.18.x.Affected if Installed version is 2026.1.6.0 or higher but lower than 2026.1.19.0
-
Verify MFA is enabled in the environmentAccess the Devolutions Server administration interface and navigate to the MFA or Two-Factor Authentication settings. Confirm whether MFA enforcement is turned on for the server or for any user accounts.Affected if MFA is enabled and users have authentication factors configured, making them potential targets for this bypass
-
Review authentication audit logs for factor bypass eventsExamine Devolutions Server authentication and security logs (typically found in the installation logs folder or via the admin console's audit view). Search for successful login events where the second factor verification was skipped or marked as not required.Affected if Logs show legitimate user accounts authenticating successfully without completing the MFA challenge when MFA is configured for those accounts
-
Check for recent user factor reconfiguration activityReview security or audit logs for events indicating users recently modified, reset, or reconfigured their authentication factors (MFA methods). Cross-reference these events with subsequent login attempts for the same users.Affected if Users have modified their MFA configuration and subsequently logged in without being prompted for the second factor
-
Identify accounts authenticating with single-factor onlyQuery the authentication logs or session records to identify any accounts that authenticated using only password/username credentials when MFA is defined as required for those accounts in the system.Affected if Any user account with enforced MFA successfully authenticated using only the first factor
You are affected if Devolutions Server version is between 2026.1.6.0 and 2026.1.18.x inclusive, MFA is enabled, and authentication logs show successful logins bypassing the configured second factor.
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.19.0
Apply vendor patch for CVE-2026-9047 which corrects the factor key state handling in the MFA management feature. Until patch is available, monitor for unauthorized access attempts and consider additional logging on authentication events.
Devolutions Server 2026.1.19.0 or later
- 1. Back up the Devolutions Server database and configuration files before proceeding with the upgrade.
- 2. Ensure all users have completed any pending MFA factor reconfiguration to avoid lockout.
- 3. Download Devolutions Server version 2026.1.19.0 or later from the official Devolutions download page at devolutions.net.
- 4. Stop the Devolutions Server service.
- 5. Install the updated version following the standard upgrade procedure documented in the Devolutions Server administration guide.
- 6. Start the Devolutions Server service and verify all services are running correctly.
- 7. Log in as an administrator and verify the MFA configuration settings are intact.
- 8. Test the MFA functionality with a test user account to confirm the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9047 — 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-9047 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