Secure Connect Gateway EUVD-2026-88749

Requires the attacker to already have local, low-privileged access (PR:L, AV:L) to a host running Dell Secure Connect Gateway Policy Manager prior to 5.34.00.16 - it is not remotely or unauthenticated-exploitable. Exploitation is further limited by high attack complexity (AC:H), implying a race condition or specific system state must be met, and by the need for the vulnerable mis-permissioned critical resource to be present in the deployed configuration. No user interaction is required (UI:N).

This is a locally-exploitable privilege-escalation flaw (CWE-732, Incorrect Permission Assignment) in Dell Secure Connect Gateway Policy Manager, patched in 5.34.00.16 per Dell advisory DSA-2026-385. The provided CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H, base 7.8) confirms it requires LOCAL access and pre-existing low privileges (PR:L) on the host - this is not remotely reachable and cannot be triggered by an unauthenticated network attacker. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The realistic risk is therefore MODERATE-and-conditional: high technical impact (full C/I/A once triggered) but gated behind local access plus, per Dell, high attack complexity (AC:H) suggesting a race condition or specific timing/state requirement. Note a possible inconsistency: Dell rates S:C (scope change) yet a permission-assignment EoP typically stays within one security authority (S:U) - verify with vendor whether the flaw crosses a scope boundary, as this materially affects the 7.8 score. Prioritize as a patch-in-normal-cycle host-hardening issue, not an emergency, unless the appliance hosts untrusted local users.

A local user who already has low-privileged shell or account access to the SCG Policy Manager host abuses a critical resource (file, directory, or service object) that was created with overly permissive access rights, modifying or replacing it to run code or gain access as a higher-privileged account. Because attack complexity is rated high, success likely depends on winning a race or hitting a specific system state. No public proof-of-concept exploit was identified at time of analysis.