Secure Connect Gateway 5.0 - Application
Dell- Product type
- Other
- Catalog vulnerabilities
- 103
en
Severity across 100 analyzed records
Verify to analyze this security profile
As of 09/13/2026, within CyStack's analyzed data, Secure Connect Gateway 5.0 - Application has 100 security vulnerabilities published in the last 90 days. Of these, 33 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Secure Connect Gateway 5.0 - Application and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-79947 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-78484 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79945 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-78493 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79735 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79693 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-79942 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-79944 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-79946 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79741 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79689 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79941 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79690 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-79736 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-79729 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-79732 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-78482 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-78483 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79731 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79950 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-79740 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-79738 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-78486 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79964 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79952 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79971 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79968 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79962 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79965 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79966CWE-532: Insertion of Sensitive Information into Log File | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-79969 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-80169 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-79638 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79694 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79728 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79961 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-78481 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79972 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-79730 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-80172 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityCritical |
CVE-2026-79970 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79692 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-78490 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-79695 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-78485 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-78489 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-78492 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-79637 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-80171 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79963 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-79635 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-79641 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-79727 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-80239 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-80174 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79974 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79967 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79973 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-79640 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-78491 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-80122 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-80175 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityLow |
CVE-2026-78494 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-79636 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-80123 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityHigh |
CVE-2026-80124 | Exploitation statusNot confirmed | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-80177 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-80055 | Exploitation statusNot known exploited | FixYes | Published09/09/2026 | SeverityMedium |
CVE-2026-80166 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-80176 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-79639 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-80125 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80167 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80126 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-79975 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80058 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80127 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-79642 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-79943 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-79691 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-79643 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-80054 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-78488 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80056 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80057 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-79644 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-79645 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-78480 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-80170 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-79734 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-78487 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80128 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80130 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-80131 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-80129 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80164 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-80238 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityCritical |
CVE-2026-80178 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityMedium |
CVE-2026-80135 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CVE-2026-80132 | Exploitation statusNot known exploited | FixYes | Published09/07/2026 | SeverityHigh |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan