dbcve.org
Remote Desktop ManagerApplication · Devolutions

CVE-2026-12162

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-16
Fix available
A fix is available. Upgrade to 2026.2.9.0 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable

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
Improper host validation in the social login autofill feature in Devolutions Remote Desktop Manager 2026.2.8 allows an attacker to disclose stored social login credentials via a crafted web entry pointing to a provider lookalike domain.

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

Devolutions Remote Desktop Manager 2026.2.8 contains improper host validation in its social login autofill feature. The application autofills stored social login credentials without properly verifying that the target web entry's domain matches the legitimate provider's domain, allowing attackers to use crafted lookalike domains to steal credentials.

MitigationImplement strict host validation to verify that the destination domain exactly matches the expected social login provider's domain before autofilling credentials. Consider implementing domain allow-listing and certificate validation.

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
Remote Desktop ManagerApplication
Affected:< 2026.2.9.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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Check Remote Desktop Manager version
    Open the application and navigate to Help > About, or check the installed version through your system's program list (Add/Remove Programs on Windows, Applications folder on macOS). Compare the version number to the affected range.
    Affected if The installed version is below 2026.2.9.0
  2. Identify social login web entries
    Open the application and browse to your saved web entries. Look for entries configured with social login providers such as Google, Microsoft, Facebook, GitHub, or similar OAuth-based authentication methods.
    Affected if Social login web entries exist in your saved entries list
  3. Inspect stored credentials for web entries
    Right-click on social login web entries and view their properties or credential storage settings. Check if login credentials are saved or configured for autofill.
    Affected if Social login web entries have stored credentials or autofill enabled
  4. Review entry domain configuration
    Examine the URL or domain field of each social login web entry. Note whether the configured domain matches the legitimate provider domain (e.g., google.com, microsoft.com, github.com).
    Affected if Social login entries point to domains that do not exactly match the legitimate provider domain, or if lookalike domains are present

You are affected if you have Remote Desktop Manager version below 2026.2.9.0 AND have social login credentials stored in web entries, regardless of whether those entries use legitimate or lookalike domains.

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 2026.2.9.0 or later
Fixed in 2026.2.9.0
Interim mitigation

Implement strict host validation to verify that the destination domain exactly matches the expected social login provider's domain before autofilling credentials. Consider implementing domain allow-listing and certificate validation.

Recommended fix High confidence

2026.2.9.0

  1. Back up your current Remote Desktop Manager configuration and data before upgrading
  2. Download Remote Desktop Manager version 2026.2.9.0 from the official Devolutions website (https://devolutions.net/remote-desktop-manager)
  3. Install or upgrade to version 2026.2.9.0 using the standard installation process
  4. Verify the installation completed successfully and the application runs without errors
  5. Test that the social login autofill feature now properly validates host domains before autofilling credentials

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

Fix this in Remote Desktop Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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