CVE-2026-73595 — Policy Manager For Secure Connect Gateway
MEDIUMCVE-2026-73595 is a medium-severity (CVSS 4.7) CWE-494 vulnerability in dell policy manager for secure connect gateway. A fix is available — see the affected versions and patch details below.
Dell Secure Connect Gateway (SCG) Policy Manager, versions prior to 5.34.00.16, Versions prior to 5.36, contains a Download of Code Without Integrity Check vulnerability. An unauthenticated…
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-73595.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-73595 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 390,400 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Description
Dell Secure Connect Gateway (SCG) Policy Manager, versions prior to 5.34.00.16, Versions prior to 5.36, contains a Download of Code Without Integrity Check vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to Code execution, Information disclosure, Information tampering, and Protection mechanism bypass.
Affected Products
policy manager for secure connect gatewaydellDetection & mitigation playbook
Vendor / applianceDetect
Inventory every dell policy manager for secure connect gateway deployment and check each version against the affected-products list above.
Fix
Apply the dell policy manager for secure connect gateway security patch or hotfix for CVE-2026-73595 on the affected version, following the vendor advisory for your exact build.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-73595 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.