CVE-2026-41120
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 · uneditedDell Wyse Management Suite, versions prior to WMS 5.5 HF1, contain an Acceptance of Extraneous Untrusted Data With Trusted Data vulnerability. A low privileged attacker with remote access could potentially exploit this vulnerability, leading to Remote Code Execution.
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 confidenceDell Wyse Management Suite versions prior to 5.5 HF1 accept untrusted input that gets processed alongside trusted data, allowing a low-privileged remote attacker to inject and execute arbitrary code on the affected system.
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< 5.5= 5.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Dell Wyse Management Suite versionAccess the Wyse Management Suite admin console or check the product version through the installed application. On the server, look for version information in the application itself, installation directory, or service information.Affected if The installed version is 5.5 or any version prior to 5.5 (e.g., 5.0, 5.1, 5.2, 5.3, 5.4). Versions prior to 5.5 and version 5.5 itself are affected.
-
Confirm network exposure of Wyse Management SuiteDetermine if the Wyse Management Suite web interface or API is accessible from remote network locations. Check firewall rules, reverse proxy configurations, or networkACLs that permit external access to the management port.Affected if The application is reachable from untrusted remote networks. The CVE states exploitation requires remote network access.
-
Verify if the vulnerable data processing feature is enabledReview the Wyse Management Suite configuration settings related to data input handling, API endpoints, or integration features that accept external data. Check if any deserialization or data parsing modules are active.Affected if Features that accept external data inputs are enabled and exposed. The vulnerability involves accepting extraneous untrusted data alongside trusted data.
-
Review user account privilegesCheck the list of configured users and their permission levels within Wyse Management Suite. Identify if any low-privileged accounts exist that should not have elevated access.Affected if Low-privileged user accounts exist with network-accessible credentials. The CVE specifies exploitation by a low-privileged attacker.
You are affected if Dell Wyse Management Suite version 5.5 or any prior version is installed and the application is accessible from remote networks where a low-privileged attacker could send malicious data payloads.
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 · scoped5.5
Upgrade to Dell Wyse Management Suite version 5.5 HF1 or later to remediate this critical vulnerability.
Wyse Management Suite 5.5 HF1
- Ensure you have a complete backup of the current Wyse Management Suite installation and database before proceeding
- Review the Wyse Management Suite 5.5 HF1 release notes and upgrade prerequisites documentation on Dell's support website
- Download WMS 5.5 HF1 from Dell's official support site (support.dell.com) using credentials with appropriate entitlement
- Stop all Wyse Management Suite services and ensure no active user sessions are running
- Install WMS 5.5 HF1 by running the upgrade installer on the WMS server(s)
- Follow the on-screen prompts to complete the installation, selecting the upgrade option when prompted
- After installation, verify all services start successfully and the web console is accessible
- Log into the admin console and verify that all managed devices are connecting properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41120 — 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-41120 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