---
id: "CVE-2026-129552"
page: "https://infrastack.ai/live/CVE-2026-129552"
kind: "vulnerability"
aliases: ["CVE-2026-129552"]
title: "Tensei auth: hard-coded JWT key lets anyone forge admin tokens"
severity: "critical"
cvss: 9.8
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "@tensei/auth", "fixed": [], "affected": "<= 0.11.5", "ecosystem": "npm"}]
ecosystems: []
tags: ["@tensei/auth", "auth-bypass", "hard-coded-credential", "headless-cms", "jwt", "node", "npm", "package", "tensei"]
not_affected_if: ["jwt-secret-set", "newer-version", "secretkey-configured"]
published_at: "2026-11-16T12:17:53+00:00"
first_seen_at: "2026-11-16T12:40:57+00:00"
updated_at: "2026-11-16T12:44:03+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-129552", "first_seen_at": "2026-11-16T12:40:57+00:00"}, {"source": "analyst", "url": "https://github.com/tenseijs/tensei/blob/630f39038c7751178465f990fb358b0c2d5b1914/packages/auth/src/index.ts", "first_seen_at": "2026-11-16T12:44:03+00:00", "cites": ["https://github.com/tenseijs/tensei/blob/630f39038c7751178465f990fb358b0c2d5b1914/packages/auth/src/index.ts"]}]
exploit_sources: []
---

# Tensei auth: hard-coded JWT key lets anyone forge admin tokens

Link for people: https://infrastack.ai/live/CVE-2026-129552 (this .md is for agents)

@tensei/auth (all releases through 0.11.5) uses the hard-coded JWT signing key 'auth-secret-key' when JWT_SECRET is unset, which is the default. Anyone who can reach the app can sign a token for any user id and be accepted as that user, including an administrator. No fix is released; the report in the maintainers' repo is still open.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- npm:@tensei/auth affected <= 0.11.5 fixed no fixed version listed

## How to check

1. Run: npm ls @tensei/auth (or grep @tensei/auth in package-lock.json / yarn.lock); versions <= 0.11.5 are affected.
2. Confirm JWT_SECRET is set to a non-empty, non-guessable value in the running process environment (not just .env.example). If unset, or set to 'auth-secret-key', you are exposed.
3. Also check whether tokensConfig.secretKey is overridden via auth().configureTokens({secretKey: ...}); if so the fallback is not used.
4. Also check SESSION_SECRET (fallback '__sessions__secret__' reported in issue #398, not in the CVE).

## Fix

No fixed version: the maintainers have not responded to issue #398 and 0.11.5 is the latest release seen. Workaround: set a long random JWT_SECRET (32+ bytes) in every environment, restart, and treat existing tokens as untrusted (the old key is public, so rotating invalidates forged ones).

## Timeline

- 2026-11-16T12:40:57+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-129552
- 2026-11-16T12:44:03+00:00 analyst https://github.com/tenseijs/tensei/blob/630f39038c7751178465f990fb358b0c2d5b1914/packages/auth/src/index.ts — VulnCheck advisory plus maintainer repo issue #398 (open, no maintainer reply, no SECURITY.md) and source at 630f390 confirm the secretKey fallback 'auth-secret-key' when JWT_SECRET is unset, so the default config is exposed. No fix released; 0.11.5 is the latest on npm.io. Nothing verified: no maintainer page. No PoC, no exploitation seen. Issue #398 also lists unauthenticated media upload, fail-open authz, CSRF, and a SESSION_SECRET fallback; those are separate unassigned reports.

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth
- [describes] tensei packages/auth/src/index.ts at 630f390 (secretKey fallback) https://github.com/tenseijs/tensei/blob/630f39038c7751178465f990fb358b0c2d5b1914/packages/auth/src/index.ts
- [discussion] tenseijs/tensei #398: Multiple high-severity vulnerabilities (open, reporter Ikram-4) https://github.com/tenseijs/tensei/issues/398

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
