External risk intelligence

Authenticated User Identity Spoofing Vulnerability Allows Account Takeover

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-18972

The vulnerability affects a GUI component of the product. Administrative GUIs and web-based management interfaces for security or infrastructure tools are commonly deployed as network-accessible services in many environments, making them reachable and potential targets for authenticated users.

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

An authenticated attacker can impersonate other users, including administrators, by manipulating a custom header in requests. This allows a low-privilege user to potentially gain full administrative control over the affected system.

  • Attackers can impersonate users via custom request headers.
  • Leadership should remember this if user impersonation is a concern.
  • Confirm if this system is used and who has low-privilege access.

Attack Path

How an attacker could exploit the issue

An attacker with existing low-privilege access can impersonate other users, including administrators, by manipulating a specific custom header. This manipulation allows them to send requests that appear to originate from a different user, potentially granting them elevated privileges and enabling account takeover. The vulnerability lies in the product's handling of user identity verification when specific metadata is provided.

  • Requires authenticated access.
  • Triggers by sending a custom header.
  • Risk of account takeover and privilege escalation.

Live Threat

Current exploitation, exposure, and threat context

An authenticated attacker could impersonate other users, including administrators, by manipulating a custom header. This could allow a lower-privileged user to gain elevated access and potentially control the system.

  • User identities and administrative control.
  • Spoofing user identity via custom header.
  • Account takeover and system compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability, which allows an authenticated attacker to impersonate other users and potentially gain administrative privileges, requires immediate attention from teams responsible for the affected GUI components and the underlying infrastructure. The first practical step is to identify all instances of the technology, assess their exposure and business criticality, and pinpoint the accountable owner to plan a risk-based remediation strategy.

  • Application and infrastructure owners should manage the issue.
  • Verify affected technology deployment and user access.
  • Plan remediation based on identified exposure.

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 software affected by CVE-2026-18972?

CVE-2026-18972 involves Velociraptor, an open-source endpoint visibility and digital forensics tool. It is widely used by security professionals to perform live response, incident investigation, and continuous monitoring across distributed systems by deploying agents that communicate with a central management server's graphical interface.

What does CVE-2026-18972 mean for system security?

This vulnerability is classified as CWE-290, which refers to Authentication Bypass by Spoofing. In plain terms, the software fails to properly verify the identity of a user when certain data is provided in a request. Because the system trusts this manipulated information, a standard user can trick the application into thinking they are someone else, such as an administrator.

How does an attacker trigger this vulnerability?

An attacker must already have an authenticated account on the system to trigger the flaw. By injecting a custom header named 'Grpc-Metadata-USER' into their network requests, they can impersonate other users. Simply browsing the site or sending standard traffic without this specific header does not trigger the identity spoofing.

Is my system at risk if it is not exposed to the internet?

Halo Surface Signal indicates this vulnerability involves a GUI component that is often reachable across a network. Even if your interface is restricted to an internal network, any user with low-level access can exploit it. Because internal threats are a primary concern here, the risk remains relevant regardless of whether the management console is public or private.

What should I do if I run this technology?

Your first step is to locate all deployments of the affected management server within your infrastructure. Review your current user access logs to understand who has low-privileged accounts and verify if any suspicious activity has occurred. Coordinate with your security engineering team to prioritize the latest software updates and confirm you are following the official configuration guidance for identity management.

References