External risk intelligence

Secure Access Server Account Creation Forgery Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-97718

The vulnerability affects a Secure Access server, a product category typically deployed as an internet-facing gateway or remote access service. Such appliances or servers are designed to be accessible from outside the internal network to facilitate remote connectivity, making it likely that the vulnerable interface is exposed to the public internet in common 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

A cross-site request forgery vulnerability in the Secure Access server could allow an attacker to trick an administrator into creating an account under the attacker's control by bypassing a security control. The main concern is confirming relevance and exposure to your environment.

  • Forged requests can create attacker-controlled accounts.
  • Understand potential unauthorized administrative access.
  • Confirm if your Secure Access server is affected.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this cross-site request forgery vulnerability by tricking an administrator into performing an action that creates an account under the attacker's command. This attack requires the attacker to lure an administrator into interacting with a malicious link or resource. Once the administrator performs the action, the attacker gains control over a newly created account.

  • Entry condition: Attacker lures admin to malicious link.
  • Trigger point: Admin performs action to create an account.
  • Resulting risk: Attacker gains control of a new account.

Live Threat

Current exploitation, exposure, and threat context

This cross-site request forgery vulnerability could allow an attacker to trick an administrator into creating a user account under the attacker's control, potentially affecting system access and administrative functions.

  • Admin-controlled accounts at risk.
  • Attacker tricks admin via forged requests.
  • Unauthorized account creation possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

This cross-site request forgery vulnerability in Secure Access server version 14.60 allows an attacker to trick an administrator into creating an account under their control. The first step is to identify all instances of the affected technology, confirm their accessibility and business criticality, and then assign ownership for remediation planning.

  • Confirm accountable owner and exposure.
  • Verify critical systems and business impact.
  • 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 is the Secure Access server software?

Secure Access server is a platform designed to manage and facilitate remote connectivity. Organizations typically use it as a gateway to provide secure access to internal network resources for remote users or devices. In version 14.60, this software manages user authentication and administrative functions, which are central to maintaining the security boundary of the infrastructure it protects.

What does CVE-2026-97718 mean?

This CVE describes a Cross-Site Request Forgery (CSRF) vulnerability. In this specific flaw, the server has a bypassed security control that fails to verify the authenticity of a request. Because of this, an attacker can craft a malicious request that, when executed by an administrator, performs an unauthorized action, such as creating a new, attacker-controlled account.

How does an attacker trigger this vulnerability?

An attacker triggers this issue by luring an administrator into interacting with a malicious link or web resource while they are logged into the Secure Access server. The bug does not trigger through automated background scanning or by simply having the server powered on; it requires the active, unintentional participation of an administrator to execute the forged request.

Is my Secure Access server at risk?

Halo Surface Signal indicates that because Secure Access servers are typically deployed as internet-facing gateways to facilitate remote connectivity, there is a high likelihood that the vulnerable interface is reachable from the public internet. If your server is configured to be accessible from outside your internal network, it faces a higher degree of risk from this type of external attack.

What should I do if I run version 14.60?

The immediate priority is to identify all instances of the Secure Access server within your environment. Once identified, confirm the specific network accessibility and business criticality of each instance. Coordinate with the designated owners of these systems to assess the impact of this account creation vulnerability and plan for appropriate remediation steps to secure administrative access.

References