Dell OpenManage Enterprise EUVD-2026-113899

Exploitation requires the attacker to already possess a valid low-privileged, remotely-reachable account on the Dell OpenManage Enterprise web console (CVSS PR:L), so this is not an unauthenticated flaw. No user interaction is needed (UI:N) and no special non-default configuration is named in the advisory. Limiting factors: a foothold account is mandatory, impact is confined to partial confidentiality (information disclosure of credentials, C:L) with no integrity or availability impact, and all affected deployments are versions prior to 4.8.0. The specific feature or endpoint that leaks the credentials is not described in the available sources.

This is a moderate-severity, low-priority issue rather than an urgent one. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3) indicates a network-reachable flaw that is easy to execute but requires an existing low-privileged authenticated account (PR:L), and the impact is limited to partial confidentiality (C:L) with no integrity or availability effect. The vulnerability class (CWE-522, Insufficiently Protected Credentials) is consistent with information disclosure of stored/handled credentials. No EPSS score was supplied, the CVE is not listed in CISA KEV, and no PoC or exploit reference is present in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The vendor-assigned priority label is 'this_month,' which aligns with the modest CVSS and the absence of exploitation signals - this is a patch-in-routine-cycle item, not an emergency. The main caveats: EPSS is entirely missing so widespread-exploitation probability cannot be quantified, and the exact credentials exposed (which account, scope, and whether they enable lateral movement) are not described in the available sources.

An attacker who already holds a low-privileged account on a Dell OpenManage Enterprise console (versions prior to 4.8.0) sends requests over the network to a function that returns or exposes insufficiently protected credentials, retrieving secret material they should not be able to read. Because scope is unchanged and impact is confidentiality-only, the immediate result is disclosure of those credentials rather than direct code execution or service disruption. No public exploit identified at time of analysis; the specific trigger is not described in the available sources.