dbcve.org
Wyse Management SuiteApplication · Dell

CVE-2026-44274

HIGH · 7.8 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 2605 or later.
See remediation →
80/100
Remediation priority · High
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
Dell Wyse Management Suite (WMS), versions prior to WMS 2605, contain an Improper Link Resolution Before File Access vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Unauthorized access.

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

Dell Wyse Management Suite versions prior to 2605 contain an Improper Link Resolution Before File Access vulnerability (also known as a symlink or TOCTOU vulnerability). A low-privileged attacker with local system access could exploit this by manipulating file system links to gain unauthorized access to sensitive files or resources that should be protected.

MitigationUpgrade Dell Wyse Management Suite to version 2605 or later to obtain the security patch addressing this vulnerability.

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
Wyse Management SuiteApplication
Affected:< 2605

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify installed Dell Wyse Management Suite version
    Locate the installation directory (typically C:\Program Files\Dell\Wyse\WMS or similar on Windows, or /opt/wysemanagement/ on Linux). Within the installation folder, look for a version file, manifest, or check the product information panel in the application itself. Alternatively, use the system's package manager or installer database to query the installed package version.
    Affected if The installed version number is less than 2605 (for example, 2505, 2409, or earlier)
  2. Verify file system permissions on the installation directory
    On Windows, right-click the installation folder, select Properties, then Security tab. On Linux, run 'ls -la' on the installation directory. Check which users or groups have Write or Modify permissions on the main application directories.
    Affected if Low-privileged users or the user group that the attacker belongs to has Write or Modify permissions on the application directories
  3. Check for symlink creation capabilities in sensitive directories
    On Windows, verify if the application directories are on drives that allow symbolic links (by default, Developer Mode or elevated privileges may be required). On Linux, test by creating a test symlink in a subdirectory of the installation folder as a low-privileged user: 'ln -s /tmp/test /path/to/installDir/testlink'.
    Affected if A low-privileged user can successfully create symbolic links within or pointing to the application's directories
  4. Inspect for existing symbolic links in the application directories
    On Windows, use 'dir /AL /S C:\Program Files\Dell\Wyse\WMS' (or your installation path) to list all symbolic links. On Linux, run 'find /opt/wysemanagement/ -type l -ls'. Review any links that point outside the expected installation tree.
    Affected if Any unexpected symbolic links exist that could be redirecting access to sensitive files or resources

You are affected if the installed Dell Wyse Management Suite version is below 2605 AND low-privileged users have the ability to create or manipulate symbolic links within the application's file system locations.

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

Upgrade Dell Wyse Management Suite to version 2605 or later to obtain the security patch addressing this vulnerability.

Recommended fix Moderate confidence

WMS 2605

  1. Verify current Wyse Management Suite version by accessing the WMS admin console or checking the installed software version
  2. Download Wyse Management Suite version 2605 from the official Dell support portal at www.dell.com
  3. Review Dell WMS upgrade documentation for version 2605 before initiating the upgrade
  4. Perform a complete backup of the WMS database and configuration settings
  5. Stop all WMS services before upgrading
  6. Install WMS version 2605 on the existing server (or follow Dell's migration guide if a new server is required)
  7. Verify all WMS services start successfully after upgrade
  8. Confirm the WMS version displays as 2605 in the admin console

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

Fix this in Wyse Management Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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