External risk intelligence

Tensei Auth Hardcoded JWT Secret Allows Impersonation

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-129552

Tensei is a framework used to build web applications and APIs. Since the vulnerability exists within the authentication component used to secure these web-facing services, it is likely that the affected surface is exposed to the internet as part of a typical web application or API deployment.

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

A vulnerability in the Tensei authentication package allows unauthenticated attackers to impersonate any user, including administrators, by signing their own tokens. This occurs because the system falls back to a hard-coded secret key when a proper one is not configured. The main concern is confirming relevance and exposure.

  • Allows attackers to impersonate users.
  • Critical to confirm if Tensei is in use.
  • Assess potential impact on user access.

Attack Path

How an attacker could exploit the issue

An attacker can impersonate any user, including administrators, by crafting a malicious JSON Web Token (JWT). This is possible because the authentication component falls back to a hard-coded secret key when a proper secret is not configured, allowing unauthenticated signing of tokens with arbitrary user identifiers.

  • No authentication is required to start.
  • Attackers can sign JWTs with any user ID.
  • Risk: Complete account takeover and privilege escalation.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, unauthenticated attackers could impersonate any user, including administrators, by signing tokens with arbitrary user IDs. This could affect access to system data, user data, and service behavior.

  • User accounts and system access at risk.
  • Attackers could sign tokens, bypassing authentication.
  • Unauthorized access and potential data exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

The authentication bypass vulnerability in Tensei's @tensei/auth package likely impacts application owners and platform teams responsible for web applications and APIs. The immediate priority is to inventory all deployments of Tensei, confirm exposure and criticality, identify the accountable team for each instance, and then collaboratively plan remediation based on the assessed risk.

  • Application owners must address this.
  • Verify JWT_SECRET configuration and reachability.
  • Plan remediation during the next maintenance window.

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 Tensei and what is it used for?

Tensei is an open-source framework designed to help developers build web applications and APIs quickly. It provides a set of pre-built tools, including the @tensei/auth package, which manages user identity and access control within those applications. Teams often use it to handle backend authentication logic so they can focus on developing custom features for their specific web services.

How does CVE-2026-129552 work?

This vulnerability is an authentication bypass classified as CWE-1394 (Use of Hard-coded Cryptographic Key). When the application is not configured with a unique secret key for signing JSON Web Tokens, the authentication component defaults to a hard-coded value. Because this key is publicly known, anyone can use it to sign their own tokens and claim to be any user, including an administrator.

What must an attacker do to trigger this vulnerability?

An attacker needs to interact with an affected application's authentication endpoint. No special privileges or prior access are required to start the attack. It is important to note that this flaw only triggers if the JWT_SECRET environment variable is not explicitly set; if the system has been configured with a unique, custom secret key, it is not vulnerable to this specific bypass.

Do I need to worry about this if my service is internal?

Yes. While Halo Surface Signal notes that Tensei services are typically web-facing and therefore likely exposed to the internet, internal applications are also at risk. If an attacker gains any foothold on your internal network, they could target the authentication service just as easily as an external actor. You should verify your configuration regardless of whether the service is public or private.

What is the first step to fix CVE-2026-129552?

Start by identifying all instances of Tensei running in your environment to understand your total footprint. Once you have a list of deployments, immediately verify the configuration of the JWT_SECRET for each instance. Ensure every production application is using a strong, unique, and non-default secret key to prevent the authentication component from falling back to the insecure hard-coded value.

References