High Cryptography

CVE-2026-35088 — Inadequate Encryption Strength in Slican telephone exchanges

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.

Published Oct 15, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: CERT-PL

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.1% (30-day exploitation probability)+0
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.12%

ahead of 2% of scored CVEs · Oct 15, 2026

Affects

Slican

CCT-1668 and 3 more

CVSS base

8.2

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Slican CCT-1668, Slican CXS-0424, Slican IPx…).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Slican	CCT-1668	≤ 6.56.0430	Vulnerable	CVE Program (cve.org) e CISA ADP
Slican	CXS-0424	≤ 6.30.0510	Vulnerable	CVE Program (cve.org) e CISA ADP
Slican	IPx	< 6.62.0100	Vulnerable	CVE Program (cve.org) e CISA ADP
Slican	MAC-6400	≤ 6.56.0430	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Attack requirements

Present

Privileges required

None

User interaction

None

Scope

Confidentiality (vulnerable system)

High

Integrity (vulnerable system)

None

Availability (vulnerable system)

None

Confidentiality (subsequent)

Low

Integrity (subsequent)

None

Availability (subsequent)

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.2	CVSS 4.0	High	—	—	cvd@cert.pl via NIST National Vulnerability Database
8.2	CVSS 4.0	High	—	—	CERT-PL via CVE Program (cve.org) e CISA ADP

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

(score shown at the top: cvd@cert.pl)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-326 · Inadequate Encryption Strength

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Check TLS negotiations and unexpected certificates in the component’s traffic.

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Affected products added · slican/ipx, slican/cct-1668, slican/mac-6400, slican/cxs-0424
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 8.2
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · Alertas do Telegram
CVE published
Oct 15, 2026 · CERT-PL

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 15, 2026 – Oct 15, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

1 on the record

cert.pl/posts/2026/10/CVE-2026-35088
third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

Slican
every CVE for this vendor

Cryptography
same class

CWE-326
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-63314 SQL Injection in WebCTI 19h
High CVE-2026-63315 Plaintext storage of a password in WebCTI 19h
Critical CVE-2026-35090 Authentication Bypass in Slican telephone exchanges May 27, 2026
Critical CVE-2026-35087 Authentication Bypass in Slican telephone exchanges May 27, 2026
High CVE-2026-35089 Use of Weak Credentials in Slican telephone exchanges May 27, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-35088 is "Inadequate Encryption Strength in Slican telephone exchanges", rated High. It affects CCT-1668 (Slican); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.2 describes technical severity. EPSS 0.12% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.