Summary
CVE-2026-80172 is a critical insufficient data-authenticity verification vulnerability (CWE-345) in Dell Secure Connect Gateway (SCG) 5.0. It allows an unauthenticated remote attacker to repeatedly replay a captured request to generate valid ADMIN access and refresh tokens, granting persistent administrative access to the SCG management environment. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).
Technical details
- Root cause: SCG does not sufficiently verify the authenticity of certain requests used to issue access/refresh tokens — there is no nonce validation and no time limit enforced on the request.
- Trigger condition: an attacker who has captured a valid request (e.g., via network interception or logs) can resend/replay it repeatedly, with each replay yielding new valid ADMIN access and refresh tokens.
- Attack vector: network-based, no authentication, no privileges, and no user interaction required (AV:N/AC:L/PR:N/UI:N).
- Impact: because replay is not time-bound or nonce-restricted, an attacker can mint administrative tokens indefinitely, resulting in complete loss of confidentiality, integrity, and availability of the SCG management plane.
Affected software
- Dell Secure Connect Gateway 5.0 – Application: versions prior to 5.36.00.00
- Dell Secure Connect Gateway 5.0 – Appliance: versions prior to 5.36.00.16
Severity
- CVSS v3.1 Base Score: 9.8 (Critical)
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: upgrade Dell Secure Connect Gateway 5.0 Application to version 5.36.00.00 or later, and SCG 5.0 Appliance to version 5.36.00.16 or later, per Dell Security Advisory DSA-2026-382.
- If patching cannot be performed immediately: restrict network exposure of SCG management interfaces (remove from the public internet, restrict to trusted management networks/VPN), and monitor for repeated/replayed authentication requests as SCG connects Dell hardware to Dell support services and often sits deep within data-center and enterprise networks.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Raw response body:
<base href="/SecureConnectGateway/resx/"> - Page title:
Secure Connect Gateway

