Cyber Resilience

CVE-2026-23859

Dell Wyse Management Suite ≤ 5.5

Published
24 February 2026
Modified
25 February 2026
Patch / advisory
CVSS Score v3.1 2.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0025 16th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-23859 is a low-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability in Dell Wyse Management Suite. Its CVSS base score is 2.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Dell Wyse Management Suite, versions prior to WMS 5.5, contain a Client-Side Enforcement of Server-Side Security vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability to Protection mechanism bypass.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Why these techniques?

Remote management application bypass enables exploitation of public-facing service (T1190); high-priv requirement and vague bypass description limit additional mappings.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-41120Same product: Dell Wyse Management Suite
CVE-2026-44271Same product: Dell Wyse Management Suite
CVE-2026-44272Same product: Dell Wyse Management Suite
CVE-2026-49506Same product: Dell Wyse Management Suite
CVE-2026-22766Same product: Dell Wyse Management Suite
CVE-2025-36580Same product: Dell Wyse Management Suite
CVE-2025-27695Same product: Dell Wyse Management Suite
CVE-2025-29981Same product: Dell Wyse Management Suite
CVE-2025-36577Same product: Dell Wyse Management Suite
CVE-2023-32482Same product: Dell Wyse Management Suite

Affected Assets

dell
wyse management suite
≤ 5.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-4 Information Flow Enforcement
  • AC-25 Reference Monitor
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V10.7.1
  • V2.2.2
  • V8.3.1
  • V10.4.1

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires server-side enforcement of access decisions rather than trusting client-side checks that can be bypassed.

prevent

Mandates server-enforced information flow policies so that protection mechanisms cannot be evaded by client-side logic.

prevent

Requires a tamper-proof reference monitor that is always invoked, eliminating reliance on client-side security enforcement.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent design flaws that place server security enforcement on the client.

PR.AA-05 partial match
prevents

Proper policy-based enforcement of authorizations implies server-side controls rather than client-only checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure architecture principles discourage client-side trust but do not directly address this weakness.

detects

Security testing can detect client-side enforcement but is not the primary mitigation.

prevents

Information access restriction is undermined when the client is trusted to enforce it.

prevents

Secure development lifecycle mandates server-side validation and prevents reliance on client enforcement.

prevents

Application security requirements explicitly call for server-side enforcement of security mechanisms.

prevents

Secure coding standards require server-side checks and reject client-only enforcement.

References