dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-0610

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-19
Fix available
A fix is available. Upgrade to 2025.3.14.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SQL Injection vulnerability in remote-sessions in Devolutions Server.This issue affects Devolutions Server 2025.3.1 through 2025.3.12

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 confidence

SQL injection vulnerability in the remote-sessions component of Devolutions Server allows attackers to inject malicious SQL queries, potentially leading to unauthorized data access, data manipulation, or complete database compromise. The critical CVSS 9.8 score indicates the vulnerability is remotely exploitable and likely requires no authentication.

MitigationUpdate Devolutions Server to a version beyond 2025.3.12 once the patched release is available. Until then, restrict network access to the server and monitor for suspicious SQL patterns in logs.

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
Devolutions ServerApplication
Affected:>= 2025.3.1.0, < 2025.3.14.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Devolutions Server version
    Locate and inspect the installed Devolutions Server version through the application itself, its service information, or installed program metadata. Check the About or Version section in the server administration interface if accessible.
    Affected if The installed version is 2025.3.1.0 through 2025.3.13.x (any version >= 2025.3.1.0 but < 2025.3.14.0)
  2. Confirm remote-sessions component is exposed
    Identify whether the remote-sessions functionality is accessible. This component typically handles RDP/VNC/SSH session management and may be exposed via the server's web interface or API endpoints. Check network exposure settings and firewall rules.
    Affected if The remote-sessions component is accessible over the network without additional authentication barriers beyond basic server access
  3. Review application and database logs for suspicious SQL patterns
    Examine Devolutions Server logs and database transaction logs for unusual SQL syntax, especially UNION-based queries, OR 1=1 patterns, or unexpected table/column name references within session-related operations. Focus on timestamps and source IPs for remote-session requests.
    Affected if Logs contain SQL injection signatures or anomalous SQL queries originating from session-related endpoints
  4. Check for unauthorized data access or manipulation
    Query the database for recent unauthorized account creations, privilege escalations, unexpected data exports, or modifications to session recordings and credentials tables that were not initiated by legitimate administrators.
    Affected if Database contains unauthorized changes or access patterns inconsistent with documented administrative activities

A user is affected if their Devolutions Server installation falls within version 2025.3.1.0 through 2025.3.13.x and the remote-sessions component is network-accessible, or if indicators of SQL injection are found in logs or database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025.3.14.0 or later
Fixed in 2025.3.14.0
Interim mitigation

Update Devolutions Server to a version beyond 2025.3.12 once the patched release is available. Until then, restrict network access to the server and monitor for suspicious SQL patterns in logs.

Recommended fix High confidence

Devolutions Server 2025.3.14.0 or later

  1. 1. Back up your current Devolutions Server database and configuration.
  2. 2. Download Devolutions Server version 2025.3.14.0 or later from the official Devolutions website (devolutions.net).
  3. 3. Stop the Devolutions Server service before applying the update.
  4. 4. Run the installer for the new version and follow the on-screen upgrade instructions.
  5. 5. After installation, verify the service starts successfully.
  6. 6. Test that remote session functionality works correctly after the upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0610 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0610 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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