External risk intelligence

Slican Telephone Exchanges Remote Control Panel Access

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-35090

The vulnerability affects telephone exchange systems that provide remote management capabilities. As these systems are designed to interface with telecommunications networks for remote administrative access and control, they are commonly exposed or reachable via the network, making them a likely target for remote exploitation in typical deployment scenarios.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in Slican telephone exchanges, allowing unauthenticated remote access to sensitive system controls. An attacker can exploit this by making a specific phone call, bypassing authentication and gaining full administrative privileges over the system's configuration and protocols. This issue is particularly concerning for older, end-of-life systems that will not receive updates, potentially requiring hardware replacement for mitigation.

  • Unauthenticated remote system control is possible.
  • End-of-life systems are permanently vulnerable.
  • Assess and upgrade legacy telephone exchanges.

Attack Path

How an attacker could exploit the issue

An attacker can target Slican telephone exchanges by initiating a connection with a specific caller ID. This allows them to bypass authentication and gain full access to the control panel and service protocols, even if remote access is normally disabled. This can lead to unauthorized management of the system.

  • Unauthenticated remote access required.
  • Specific caller ID triggers vulnerability.
  • Full system control is at risk.

Live Threat

Current exploitation, exposure, and threat context

An unauthenticated attacker could gain full control over Slican telephone exchanges by connecting via a modem with a specific caller ID, even temporarily enabling remote access if disabled. This bypasses authentication, exposing the service protocol and configuration panel for remote management.

  • Telephone exchange control panel.
  • Remote connection via caller ID.
  • Full administrative access gained.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world ownership of this vulnerability likely falls to teams managing the Slican telephone exchange systems, potentially including IT infrastructure, telecommunications, or specialized network operations teams. The initial practical step is to inventory all deployed Slican systems, determine their network reachability and business criticality, and identify the accountable owner for each. This will inform a risk-based remediation plan, prioritizing systems that are accessible and essential.

  • Identify telecommunication system owners.
  • Verify remote access and network exposure.
  • Contact vendor for hardware upgrade options.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What are Slican telephone exchanges?

Slican telephone exchanges are telecommunications systems used to manage voice communications and office telephone infrastructure. These devices act as a central hub for call routing and feature administrative interfaces that allow technicians to configure system protocols, manage user settings, and maintain service operations remotely.

What does CWE-288 mean for CVE-2026-35090?

CWE-288 refers to an authentication bypass vulnerability using an alternate path or channel. In the context of CVE-2026-35090, it means the system incorrectly trusts a specific telephone caller ID as a substitute for valid administrative credentials. This weakness allows an unauthorized person to effectively 'log in' to the control panel by simply presenting the correct identifier through a phone connection, bypassing the security gate entirely.

How is the vulnerability triggered?

An attacker initiates the vulnerability by connecting to the telephone exchange’s modem using a device configured with a specific, crafted caller ID. This action bypasses the need for a password or legitimate admin token. Notably, the bug does not require any existing remote access features to be active; if the system is currently set to block remote management, the specific caller ID will force that access to turn on automatically.

Why is this relevant to my infrastructure?

According to Halo Surface Signal, this vulnerability is considered a likely target because these systems are designed to bridge telephone networks with management interfaces. Since these exchanges are frequently reachable via broader networks for administrative convenience, they may be exposed to remote callers, making it possible for unauthorized individuals to gain full administrative control over the exchange’s configuration.

What is the first step to address this risk?

Start by creating an inventory of all Slican equipment in your environment to identify which specific models and firmware versions are in use. Check your systems against the affected version list in this advisory. If you are using legacy devices that have reached the end of their support life and cannot be patched, contact the vendor’s service department immediately to discuss hardware upgrade paths to secure your communications.

References