CVE-2026-129552
9.8CriticalPublished 16 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
Critical
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-1394
What an attacker gets
Unauthenticated attackers can impersonate any user, including administrators, by signing their own JWTs. This requires no prior access or user interaction.
Root cause
The application falls back to a hard-coded default string 'auth-secret-key' when the JWT_SECRET environment variable is not configured.
Affected versions
Tensei through 0.11.5
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade to a version beyond 0.11.5. Immediately set the JWT_SECRET environment variable to a strong, unique random string in your production environment.
$ npm list @tensei/authAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.
References
- https://github.com/tenseijs/tensei
- https://github.com/tenseijs/tensei/blob/630f39038c7751178465f990fb358b0c2d5b1914/packages/auth/src/index.ts#L94-L98
- https://github.com/tenseijs/tensei/issues/398
- https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth