CVE-2026-129552 in Tenseiinfo

Summary

by MITRE • 11/16/2026

Tensei through 0.11.5 contains an authentication bypass vulnerability in @tensei/auth that falls back to the hard-coded JWT signing key 'auth-secret-key' when JWT_SECRET is unset. Unauthenticated attackers can sign tokens with arbitrary user ids accepted by populateContextFromToken to impersonate any user, including administrators.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/16/2026

The identified security flaw resides within the authentication module of Tensei versions through 0.11.5, specifically affecting the @tensei/auth package. This vulnerability constitutes a critical authentication bypass that allows unauthenticated actors to assume the identity of any user on the system. The root cause is rooted in improper handling of environment variables during the initialization of JSON Web Token verification logic. When the JWT_SECRET environment variable is not explicitly defined or remains unset, the application fails to enforce strict configuration requirements and instead reverts to a hard-coded default signing key known as auth-secret-key. This fallback mechanism represents a severe misconfiguration that undermines the fundamental security model of token-based authentication systems.

From a technical perspective, JSON Web Tokens rely on cryptographic signatures to ensure integrity and authenticity. In this scenario, because the secret key is static and publicly documented or easily discoverable within the source code, attackers can independently generate valid JWTs without possessing any legitimate credentials. By utilizing the known auth-secret-key, an adversary can craft tokens containing arbitrary claims, specifically targeting the user identifier fields that are processed by the populateContextFromToken function. This function accepts these forged tokens and maps them to internal session contexts, effectively granting the attacker full access privileges associated with the specified user ID. The vulnerability exploits the lack of input validation regarding configuration states, allowing a simple absence of environment variables to trigger a catastrophic security failure rather than raising an error or refusing service.

The operational impact of this flaw is severe and potentially devastating for any deployment relying on Tensei for identity management. Since the attack vector requires no prior authentication, it enables complete unauthorized access to protected resources. An attacker can impersonate standard users to exfiltrate sensitive data, modify records, or execute actions on behalf of victims. More critically, because the vulnerability allows arbitrary user ID injection, attackers can directly target administrative accounts. By signing a token with an administrator's user identifier, the adversary gains full control over the application backend, potentially leading to total system compromise, persistent backdoor installation, and widespread data breaches. This level of access bypasses all intended security controls, rendering any other defensive measures ineffective if this specific authentication path is utilized.

This vulnerability aligns closely with CWE-287, which describes Improper Authentication, as the software fails to correctly verify identity before granting access. Furthermore, it relates to CWE-798, Use of Hard-coded Credentials, due to the reliance on a static secret key that serves as a single point of failure for authentication integrity. In terms of offensive security frameworks, this flaw facilitates ATT&CK technique T1078, Valid Accounts, by allowing attackers to obtain legitimate-looking credentials through forgery rather than theft or brute force. It also touches upon T1528, Steal Application Access Token, as the attacker generates valid tokens that are indistinguishable from those issued by the server itself.

To mitigate this vulnerability, immediate action is required for all systems running affected versions of Tensei. The primary remediation step involves upgrading to a patched version where the authentication module enforces mandatory configuration of JWT_SECRET and rejects requests if it remains unset. For organizations unable to upgrade immediately, applying a temporary workaround by explicitly setting a strong, randomly generated JWT_SECRET environment variable in the deployment configuration is essential. This ensures that the application does not fall back to the insecure default key. Additionally, security teams should audit their CI/CD pipelines to ensure secret management practices do not leave critical variables undefined during runtime initialization. Regular rotation of signing keys and implementing strict validation checks for all authentication-related configurations will further harden the system against similar misconfiguration attacks in the future.

Responsible

VulnCheck

Reservation

11/16/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!