External risk intelligence

Raisecom SSH Authentication Bypass Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2025-11534

The vulnerability affects Raisecom network devices, which typically function as edge gateways, routers, or switches. These devices frequently expose management interfaces, such as SSH, to the network. While best practices dictate limiting management access, these interfaces are commonly reachable across network perimeters in many real-world deployments of networking hardware.

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

The affected Raisecom devices have a security flaw that allows unauthorized access to their command interface without proper user authentication, potentially enabling attackers to gain control.

  • Unauthenticated shell access is possible.
  • Critical network devices may be compromised.
  • Confirm relevance and exposure to our infrastructure.

Attack Path

How an attacker could exploit the issue

Attackers can reach Raisecom devices and establish SSH sessions without needing valid credentials, potentially leading to unauthorized shell access.

  • Network access is required.
  • Unauthenticated SSH session is triggered.
  • Unauthorized shell access is the risk.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthorized individuals to gain shell access to affected Raisecom devices by bypassing user authentication over SSH. This could impact device configuration and network traffic when such access is obtained.

  • Device configuration and control at risk.
  • Unauthorized access via SSH network connection.
  • Potential for unauthorized device or network changes.

Operational Fix

Recommended remediation, mitigation, and detection steps

The presence of an unauthenticated SSH access vulnerability on Raisecom devices suggests that infrastructure and network security teams are primarily responsible for remediation. The immediate first step is to identify all deployed Raisecom devices, determine their network reachability and business criticality, and then confirm the accountable owner for each instance before planning a coordinated response.

  • Network and infrastructure teams own the issue.
  • Verify device reachability and criticality.
  • Plan remediation based on identified risk.

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 Raisecom devices and why are they used?

Raisecom devices are networking hardware often deployed as routers, switches, or edge gateways. Organizations use them to manage network traffic, connect different network segments, and provide essential connectivity for business operations. They act as fundamental infrastructure components that bridge local networks to wider environments.

What does CVE-2025-11534 mean for system security?

This vulnerability is classified as an authentication bypass (CWE-288). In plain terms, it means the security mechanism responsible for verifying who is logging into the device fails. Because of this flaw, an attacker can establish an SSH session and gain command-line access to the device without providing a username or password.

How is this SSH bypass triggered?

The vulnerability is triggered when a connection is initiated to the device's SSH service. Because the flaw exists within the authentication logic itself, an attacker does not need to guess credentials or exploit other software bugs. Simply initiating a standard SSH request is sufficient to bypass the login requirement; local console physical access is not required to trigger this.

Is my organization at risk from this CVE?

If you use Raisecom devices, you are potentially at risk. According to Halo Surface Signal, these devices frequently function as edge gateways and are commonly reachable across network perimeters. If your management interfaces are exposed to the internet or wide internal network segments, the likelihood of unauthorized access is higher.

What should I do if I run affected Raisecom hardware?

Start by creating an inventory of all Raisecom devices in your environment to understand your footprint. Prioritize identifying which units are reachable over the network and determine their business criticality. Once mapped, coordinate with your infrastructure teams to assess these devices, confirm the accountable owner for each, and prepare for necessary updates or configuration changes.

References