Dell Secure Connect Gateway EUVD-2026-95571

Exploitation requires network reachability to the Dell SCG Policy Manager interface and the ability to induce an application error whose message leaks sensitive data; per CWE-209 the leak occurs through generated error messages. The CVSS high attack complexity (AC:H) indicates a key limiting factor: the attacker must engineer specific, non-trivial conditions to reliably provoke the revealing error, and the impact is confined to confidentiality (C:L) with no integrity or availability effect. No authentication is required (PR:N) and no user interaction is needed (UI:N), but the practical reach is limited to the information incidentally exposed in error output rather than arbitrary data access.

This is a genuinely low-priority issue, and the signals are internally consistent rather than conflicting. The vendor-assigned CVSS 3.1 vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) yields a base score of 3.7 (Low): although the attack vector is network-based and requires no privileges or user interaction, the high attack complexity (AC:H) and the limited confidentiality-only impact (C:L, with no integrity or availability effect) sharply constrain real-world severity. No EPSS score, KEV listing, POC, or SSVC decision data was supplied in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The absence of these signals is itself consistent with a low-value information-disclosure bug (CWE-209) that leaks fragments of sensitive data via error messages rather than enabling code execution or full data compromise. Bottom line: a real but minor hygiene/defense-in-depth fix, not an emergency; patch on a normal cycle. Note the low CVSS is driven by AC:H and C:L - the network/unauthenticated reachability means it should not be ignored entirely, especially if the Policy Manager is internet-facing.

A remote, unauthenticated attacker repeatedly sends malformed or edge-case requests to the Dell SCG Policy Manager to provoke application errors, then reads the returned error messages which disclose sensitive internal information (e.g., stack traces, configuration details, or internal paths). The high attack complexity (AC:H) means the attacker must craft specific conditions to trigger the revealing errors, and no public exploit code is known at time of analysis.