Menu

Star on GitHub · 3.4k

CVE-2026-35088

Slican telephone exchanges use symmetric encryption for TCP/IP communication.

Published Oct 15, 2026CWE-326EPSS 0.12%

Overview

CVE-2026-35088 is a known-severity vulnerability. It was published on October 15, 2026.

Technical description

Slican telephone exchanges use symmetric encryption for TCP/IP communication. Secret key is hardcoded in multiple binary files. An attacker who has access to these files can decrypt the communication.

This issue was fixed in IPx series version 6.62.0100.

The issue STILL EXISTS in End-Of-Life telephone exchanges:

- CCT-1668 (CCT1CPU)

- MAC-6400

- CXS-0424

These products were discontinued in 2011 and 2012 and and will not receive updates. These products require a hardware update in order to receive a software update. The vendor recommends that users of these devices contact the their service department directly to determine the options for upgrading.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-35088?

CVE-2026-35088 is a known-severity vulnerability. It was published on October 15, 2026.

How severe is CVE-2026-35088?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-35088?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-35088?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-35088 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Watch the demo →