dbcve.org
Devolutions ServerApplication · Devolutions

CVE-2026-1007

HIGH · 7.6 CVSS v3.1 Published 2026-01-19
Fix available
A fix is available. Upgrade to 2025.3.14.0 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable 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
Incorrect Authorization vulnerability in virtual gateway component in Devolutions Server allows attackers to bypass deny IP rules.This issue affects Server: from 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 · high confidence

An incorrect authorization vulnerability in the virtual gateway component of Devolutions Server allows attackers to bypass configured IP deny rules. The virtual gateway fails to properly enforce IP-based access controls, potentially allowing unauthorized access from blocked IP addresses.

MitigationUpgrade Devolutions Server to a version beyond 2025.3.12, or apply vendor-provided patches. Review and monitor access logs for any suspicious connections from blocked IP ranges.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:H/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 checks

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

  1. Identify installed Devolutions Server version
    Locate the Devolutions Server installation and check the version number. This is typically found in the product UI under 'About' or 'System Information', or in the installation directory's version file. Compare against the affected range: 2025.3.1.0 through 2025.3.13.x.
    Affected if The installed version is 2025.3.1.0 or higher but lower than 2025.3.14.0.
  2. Confirm Virtual Gateway feature is in use
    Verify whether the Virtual Gateway component is enabled or configured in your Devolutions Server deployment. Check the server configuration settings or admin console for Virtual Gateway status.
    Affected if Virtual Gateway is enabled and accepting connections.
  3. Identify configured IP deny rules
    Review the Devolutions Server security or access control settings to document any IP deny rules that are configured to block specific IP addresses or ranges.
    Affected if IP deny rules are defined in the Virtual Gateway configuration.
  4. Review access logs for potential bypass indicators
    Examine Devolutions Server access and audit logs for connections originating from IP addresses that should be denied by your configured rules. Look for successful authentication or session establishment from blocked IPs.
    Affected if Logs show connections from blocked IP addresses that were allowed through the Virtual Gateway.

A user is affected if they run Devolutions Server version 2025.3.1.0 through 2025.3.13.x with the Virtual Gateway enabled and have IP deny rules configured, as the vulnerability allows those rules to be bypassed.

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

Upgrade Devolutions Server to a version beyond 2025.3.12, or apply vendor-provided patches. Review and monitor access logs for any suspicious connections from blocked IP ranges.

Recommended fix High confidence

Devolutions Server 2025.3.14.0 or later

  1. Identify the current Devolutions Server version running in your environment
  2. Create a complete backup of the Devolutions Server database and configuration files
  3. Download Devolutions Server version 2025.3.14.0 or later from the official Devolutions download center (https://devolutions.net/server/)
  4. Follow the official Devolutions Server upgrade documentation to apply the update to your environment
  5. After upgrading, verify that deny IP rules are now properly enforced in the virtual gateway component
  6. Test that the authorization bypass is no longer present by attempting to access resources from IP addresses that should be denied

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

Fix this in Devolutions Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1007 — 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-1007 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