External risk intelligence

Bastillion Authentication Bypass via Path Prefix Routing Mismatch

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-75627

Bastillion is a web-based SSH gateway designed for centralized management and access to server fleets. As an identity portal and remote access service, its primary function necessitates exposure as an internet-facing gateway, making it highly likely to be deployed in a manner that is reachable from the public internet.

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Bastillion's request handling could allow unauthorized access to administrative functions, potentially leading to the creation of new manager accounts and the registration of managed systems, thereby enabling control over SSH access to connected servers.

  • Unauthenticated users can bypass controls.
  • Centralized SSH management system compromised.
  • Confirm relevance and scope immediately.

Attack Path

How an attacker could exploit the issue

Attackers can leverage an unvalidated request path to bypass Bastillion's authentication. This allows them to access administrative functions, such as creating new manager accounts or listing users, ultimately leading to control over the managed systems.

  • No authentication required to start.
  • Triggered by manipulating request URIs.
  • Risk of unauthorized administrative access.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated attackers to bypass security measures and gain administrative control over the Bastillion system. This could lead to unauthorized access to user information and the ability to manage connected SSH systems.

  • Administrative controllers and user data are at risk.
  • Attackers can prefix URIs to bypass authentication.
  • Unauthorized control over managed SSH systems.

Operational Fix

Recommended remediation, mitigation, and detection steps

Bastillion's authentication bypass vulnerability requires immediate attention from teams managing infrastructure and application security. The first step is to locate all instances of Bastillion, determine their reachability and criticality, and identify the accountable owners before planning remediation.

  • Ownership: Infrastructure and application security teams.
  • Verify first: Bastillion instances and their reachability.
  • Action: Plan and execute remediation based on 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 Bastillion and why is it used?

Bastillion is a web-based SSH gateway that acts as a centralized management portal. It allows administrators to connect to and manage fleets of servers through a single interface, essentially serving as a bridge between users and remote systems. Because it consolidates administrative control over SSH access, it is a critical component for infrastructure management.

How does this CVE-2026-75627 vulnerability work?

This flaw is an authentication bypass, categorized as CWE-288. It occurs because the software fails to properly check the URI path of incoming requests in its controller dispatcher. By adding specific prefixes to a request path, an unauthorized user can trick the system into skipping its standard security checks, allowing them to reach administrative functions that should be restricted.

Do I need to authenticate to trigger this bug?

No, this vulnerability does not require any existing account or login. An attacker can initiate this by sending specially crafted, unauthenticated requests to the web server. The bug is specifically triggered by manipulating the request URI path; simply browsing the application normally or sending standard, valid requests without these crafted path modifications does not trigger the flaw.

Is my instance at risk if it is internet-facing?

Yes, if your Bastillion instance is accessible from the public internet, it faces a higher risk. According to Halo Surface Signal, because Bastillion is designed as a centralized identity and remote access service, these systems are typically deployed to be reachable from outside the internal network, making them prime targets for unauthorized access attempts if left unprotected.

When should I prioritize addressing this?

You should prioritize this immediately, as the vulnerability allows for full administrative control, including the ability to add new manager accounts and hijack SSH access to your entire server fleet. Start by auditing your environment to identify all active Bastillion instances, confirm who owns them, and evaluate their network reachability to begin your security response.

References