CVE-2026-15642 in Devolutions Server
Insertion of sensitive information into a file in the Recovery Kit response file generation feature in Devolutions Server 2026.1.22.0, 2026.2.11.0 allows an attacker with access to the generated response file to obtain the Azure Key Vault client secret in cleartext, even when the option to exclude sensitive data is selected.
Quick answer
Devolutions Server should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Devolutions Server 2026.1 before 2026.1.23.0
- Devolutions Server 2026.2 before 2026.2.12.0
Fixed versions
- 2026.1.23.0
- 2026.2.12.0
How to fix it
CVE-2026-15642 is a information disclosure issue in Devolutions Server. Update from Devolutions Server 2026.1 before 2026.1.23.0 to 2026.1.23.0 or newer. Keep it simple: upgrade first, then test the normal user flow.
- Find every place where Devolutions Server is installed or used.
- Upgrade Devolutions Server to 2026.1.23.0 or a newer fixed release from the vendor.
- If you cannot upgrade right away, limit access to the affected feature until the update is done.
- Restart or redeploy the service if the product needs it after the update.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is 2026.1.23.0 or newer.
- Run a normal login, admin, and user flow to make sure the site still works.
- Check logs for new errors after the update.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-15642?
Devolutions Server versions listed as affected should be reviewed: Devolutions Server 2026.1 before 2026.1.23.0, Devolutions Server 2026.2 before 2026.2.12.0.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.