CVE-2026-129552: Tensei through 0.11.5 Authentication Bypass via Hard-Coded JWT Secret in @tensei/auth
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 JWTSECRET is unset. Unauthenticated attackers can sign tokens with arbitrary user ids accepted by populateContextFromToken to impersonate any user, including administrators.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments using @tensei/auth through version 0.11.5 are exposed when JWT_SECRET is unset, causing the component to use the hard-coded signing key auth-secret-key.
What does an attacker need to exploit it?
An attacker does not need authentication or user interaction. They can sign a JWT using the known fallback key and supply an arbitrary user ID accepted by populateContextFromToken.
What is the potential impact of successful exploitation?
An attacker can impersonate any user whose ID is accepted, including an administrator. This can result in compromise of confidentiality, integrity, and availability.
What can be done if upgrading is not immediately possible?
Ensure JWT_SECRET is explicitly set to a strong, non-default secret so @tensei/auth does not fall back to auth-secret-key.