External risk intelligence

Tensei Auth Privilege Escalation via Self Assigned Roles

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-129550

The vulnerability exists in an authentication module for a web framework. Such components are typically used to build user-facing web applications or APIs that are exposed to the public internet to handle registration and authentication processes.

Privilege Escalation

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 vulnerability in the Tensei authentication module allows unauthorized users to gain administrator privileges by assigning themselves arbitrary roles. It affects technologies related to user management and authentication within the Tensei framework. The primary concern is confirming if this specific component is in use and identifying any potential exposure.

  • Unauthenticated users can gain admin access.
  • Critical for protecting user data and system integrity.
  • Confirm if Tensei auth is in use and exposed.

Attack Path

How an attacker could exploit the issue

Attackers can exploit this vulnerability by sending specially crafted requests to the authentication component of Tensei. Since the User Roles field is exposed, attackers can assign themselves administrative privileges during account creation, by posting to the user route, or by modifying their own user record. This could allow an unauthenticated or authenticated attacker to gain full control over the system.

  • No authentication required to start.
  • Modifies user roles via API endpoints.
  • Leads to administrative privilege escalation.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthenticated or authenticated users to gain administrator privileges within the Tensei system by manipulating role assignments during user registration or profile updates. When supported by the advisory, this could affect user account data and system access controls.

  • System access and user roles.
  • Via direct manipulation of user data.
  • Unauthorized administrator control.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world action will likely fall to the platform or application teams responsible for the Tensei framework and any applications built with it. The first practical step is to identify all instances of Tensei, assess their exposure and criticality, and confirm ownership. This will enable a risk-based remediation plan, potentially involving vendor coordination or temporary risk reduction measures.

  • Identify affected Tensei instances.
  • Verify instance exposure and business criticality.
  • Plan and execute remediation strategy.

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 Tensei framework?

Tensei is a headless CMS and real-time framework designed to help developers build backend services, APIs, and administrative interfaces rapidly. It utilizes a modular architecture, including specialized packages like @tensei/auth, which handles essential functions such as user registration, profile management, and role-based access control within applications built on the platform.

What does CVE-2026-129550 mean for Tensei security?

This vulnerability is classified as CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes. In plain English, the system fails to verify whether a user has permission to set their own security roles. Because the application logic trusts input provided by the client during registration or profile updates, it allows anyone to elevate their account status to administrator without authorization.

How do attackers trigger this Tensei privilege escalation?

An attacker triggers the flaw by including an unexpected 'roles' array in the data sent to specific API endpoints. This includes the initial account registration POST request, general user creation routes, or PATCH requests when updating an existing user record. Note that this does not require complex bypasses; the vulnerability is triggered simply by supplying the role information during standard API interactions, as the server blindly applies these fields.

Is my Tensei instance at risk?

Halo Surface Signal indicates that because this vulnerability exists within an authentication module, any application using Tensei to handle public-facing user registration or profile management is a potential target. If your application exposes these authentication routes to the public internet, it faces a higher likelihood of being targeted compared to instances strictly limited to internal, private networks.

What are the first steps to address this CVE?

Start by identifying all deployed instances of the Tensei framework within your environment to determine where the @tensei/auth package is actively in use. Once identified, evaluate the criticality of those specific applications and confirm which teams are responsible for managing them. This inventory allows you to coordinate with development teams to verify if the affected authentication logic is exposed and to prioritize the application of necessary vendor-provided updates.

References