External risk intelligence

Ghost Authentication Bypass Allows OAuth Token Theft

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-130070

The vulnerability exists in an API endpoint responsible for user sessions and authentication processes. APIs and web application endpoints that handle session creation and authentication are commonly deployed as internet-facing services to facilitate user access, making this reachable surface likely to be exposed to the public internet in typical web application deployments.

Authentication Bypass

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 an authentication bypass vulnerability found in a specific software component related to user session management. The flaw allows unauthorized access to user accounts by bypassing a verification step. The primary concern is to determine if this technology is in use and if it is exposed externally.

  • Bypasses security to take over accounts.
  • Protects against unauthorized account access.
  • Confirm technology use and external exposure.

Attack Path

How an attacker could exploit the issue

An attacker can begin by obtaining a session from a publicly accessible endpoint. This session can then be used to call a specific method, providing an arbitrary email address and a parameter to bypass OTP verification. This process allows the attacker to gain access to existing user accounts by obtaining their OAuth tokens.

  • Unauthenticated network access required.
  • Bypass OTP verification in API call.
  • Account takeover via OAuth tokens.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated attackers to bypass OTP verification and take over existing user accounts by exploiting a flaw in the `convert_to_real_user` method. An attacker could first obtain a ghost session from a publicly accessible endpoint, then use this session to call the vulnerable method with a fabricated email and a bypass parameter, ultimately receiving OAuth tokens for an existing account.

  • User accounts and session data.
  • Bypassing OTP via API calls.
  • Unauthorized account access and control.

Operational Fix

Recommended remediation, mitigation, and detection steps

The application owner is responsible for assessing the impact of this authentication bypass vulnerability. The first step is to identify all instances of the affected code, determine if they are accessible externally or handle sensitive data, and then assign an owner for remediation.

  • Identify all affected code instances.
  • Verify external reachability and data sensitivity.
  • 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 Ghost software component affected by CVE-2026-130070?

Ghost is a software project by muneeb141 that provides API-based user session and account management functionality. It includes features for handling authentication flows, such as guest sessions and converting them into authenticated real-user sessions. The affected code is located on the main branch within the library's API module, specifically involving how the system transitions users from guest status to verified real-world account holders.

How does this vulnerability allow for account takeover?

This flaw is an authentication bypass, classified as CWE-807 (Reliance on Untrusted Inputs in a Security Decision). It occurs because the API method intended to upgrade guest sessions does not strictly enforce security checks. By sending a specific 'bypass_otp' parameter to the API, an unauthorized actor can force the system to skip necessary verification, tricking the server into issuing valid OAuth tokens for an account that belongs to someone else.

Do I need to authenticate to trigger this flaw?

No, you do not need prior authentication to trigger this vulnerability. The attack path begins at a guest-accessible endpoint that allows anyone to establish a ghost session. Once that session is obtained, the attacker can immediately call the vulnerable conversion method. The bug is specifically triggered by the presence of a user-supplied parameter, so it cannot be triggered if that input is ignored or blocked by the application's configuration.

Is my system at risk if it uses this Ghost code?

According to Halo Surface Signal, this vulnerability is considered a likely risk because it resides in API endpoints designed to manage sessions, which are frequently exposed to the internet to support user connectivity. If your deployment makes these authentication methods accessible over the public network, an external party could attempt to exploit the logic flaw to compromise user accounts without ever needing legitimate credentials.

What is the first step to address this issue?

Begin by auditing your infrastructure to locate all instances where this specific version of the Ghost code is deployed. Prioritize checking environments that are reachable from the internet or that handle sensitive user authentication data. Once you have identified the affected instances, evaluate their exposure levels and assign a team member to manage the necessary updates or configuration changes required to secure the authentication process.

References