CVE-2026-13372
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 · uneditedIncorrect link resolution by display name in the custom PowerShell VPN editor in Devolutions Remote Desktop Manager 2026.2.5 through 2026.2.11 allows an authenticated attacker with write access to a shared workspace to execute a PowerShell script in another user's context via a display name collision with an existing VPN script link.
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 confidenceThe vulnerability exists in the custom PowerShell VPN editor's link resolution mechanism, which uses display names rather than unique identifiers to resolve VPN script links. An authenticated attacker with write access to a shared workspace can create a new VPN script entry with a display name that collides with an existing legitimate VPN script link. When other users access what they believe is the legitimate entry, the application resolves to the attacker's script instead, executing it in the victim's context.
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.2.5.0, <= 2026.2.12.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Remote Desktop Manager versionOpen Remote Desktop Manager, go to Help > About or check the application executable properties to locate the installed version number.Affected if The version falls within the range 2026.2.5.0 to 2026.2.12.0 inclusive.
-
Determine if custom PowerShell VPN scripts are configuredNavigate to the VPN settings or VPN connections panel within Remote Desktop Manager. Look for entries configured as custom PowerShell VPN scripts (typically indicated by a script type or custom provider designation).Affected if One or more custom PowerShell VPN script entries exist in the configuration.
-
Check for shared workspace usageExamine whether the VPN scripts are stored within a shared workspace, folder, or data source that multiple users can access. Look for workspace path indicators or shared data source configurations.Affected if The VPN scripts are stored in a shared workspace accessible by multiple authenticated users.
-
Inspect VPN script entries for display name collisionsReview all VPN script entries in the shared workspace. Identify any entries that share identical display names but may point to different script locations or contents.Affected if Two or more VPN script entries share the same display name, creating a collision that could resolve to an unintended script.
You are affected if Remote Desktop Manager version is between 2026.2.5.0 and 2026.2.12.0 AND custom PowerShell VPN scripts are configured in a shared workspace where display name collisions exist.
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 · scopedUpgrade to Devolutions Remote Desktop Manager version 2026.2.12 or later, which implements proper unique-identifier-based link resolution. Until patched, restrict write access to shared workspaces to trusted personnel only.
2026.2.13.0 or later
- Upgrade Remote Desktop Manager to version 2026.2.13.0 or later
- After upgrading, verify the installation by checking Help > About in Remote Desktop Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13372 — 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-13372 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