Dell Secure Connect Gateway EUVD-2026-74771

No authentication is required per the CVSS PR:N vector - the vulnerability is reachable by any remote attacker with network connectivity to the SCG service port. The SCG must be running an affected version: Appliance prior to 5.36.00.16 or Application prior to 5.36.00.00. No specific non-default configuration is described as required. Limiting factors: the SCG is typically deployed in enterprise internal networks or DMZs with connectivity back to Dell's support infrastructure, so exposure to untrusted networks depends on organizational network topology; organizations that isolate SCG behind a firewall with no direct internet ingress significantly reduce external attack surface. The precise exploitable endpoint (API port, management console, outbound certificate validation against Dell's backend) is not confirmed from available data - the advisory title references 'multiple vulnerabilities,' suggesting this is one of several issues in the same advisory.

The vendor-provided CVSS 8.2 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H) presents a notable internal inconsistency: C:N (no confidentiality impact) conflicts with the description's claim of 'unauthorized access,' which typically implies at minimum some confidentiality exposure. Either the primary exploitation path is DoS/availability disruption (consistent with A:H and C:N) with limited integrity side-effects, or the CVSS understates confidentiality impact. This discrepancy should be verified against Dell's full advisory DSA-2026-382. EPSS data is not provided, and there is no KEV listing or public POC, indicating no observed active exploitation. AC:L in the provided vector is plausible if an attacker can directly present a malformed certificate to the SCG service without needing a MITM position - for example, triggering a crash by connecting with a crafted invalid cert. However, if 'unauthorized access' implies certificate-based authentication bypass, AC:H would be more accurate (MITM positioning required). Real-world risk is meaningful for enterprises with Dell hardware fleets using SCG for remote support, since SCG typically has broad internal network reach and connectivity back to Dell's support infrastructure - a compromise of this component could affect management-plane access.

An unauthenticated remote attacker sends a TLS connection to the Dell SCG service bearing an invalid, expired, or forged certificate; the SCG fails to properly reject it due to CWE-295, either causing the service to crash (producing the A:H availability impact) or accepting the connection as legitimate and granting the attacker unauthorized access to SCG management functions. No public proof-of-concept code is known to exist at time of analysis.