How to Fix CVE-2026-3221: Server (Bundle Sibling)
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-3221 is a sibling vulnerability in the same vendor advisory as CVE-2026-1768. Apply the same patched build and you close both. The technical detail below is what differs.
| Severity | 4.9 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Server 0 to <2025.3.15 |
| Fixed in | Same patched build as CVE-2026-1768 |
| Type (CWE) | CWE-312 Cleartext Storage of Sensitive Information |
What's different about CVE-2026-3221?
Sensitive
user account information is not encrypted in the database in Devolutions Server 2025.3.14 and earlier, which allows an attacker with
access to the database to obtain sensitive user
information via direct database access.
How to fix CVE-2026-3221
Apply the patched build per the primary write-up: How to Fix CVE-2026-1768. All commands, verification steps, and rollback notes for Server are listed there.
Frequently asked questions
Does the CVE-2026-1768 patch close CVE-2026-3221?
Yes. Both CVEs are addressed by the same vendor patch. Applying the patched build closes the full bundle.
Is CVE-2026-3221 listed in CISA KEV?
No public KEV listing at the time of this writing.
Where is the official advisory?
See https://devolutions.net/security/advisories/DEVO-2026-0004/
References
- Official vendor advisory: https://devolutions.net/security/advisories/DEVO-2026-0004/
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3221
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary: How to Fix CVE-2026-1768
*Written by Sai Kiran Pandrala. Part of the Server bundle. Full procedure at how-to-fix-cve-2026-1768.*