Cyber & AI intelligence
Briefs indexed3762
Issues37
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-129552 2026-11-16

CVE-2026-129552: Hard-Coded JWT Key in Tensei Auth Allows Admin Impersonation

"Tensei through 0.11.5 falls back to a hard-coded JWT signing key when `JWT_SECRET` is unset, so unauthenticated attackers can forge tokens and impersonate any user, including administrators."

Tensei through 0.11.5 falls back to a hard-coded JWT signing key when JWT_SECRET is unset, so unauthenticated attackers can forge tokens and impersonate any user, including administrators.

What Is It

CVE-2026-129552 is an authentication bypass in the @tensei/auth package of the Tensei framework. VulnCheck disclosed it. If the JWT_SECRET environment variable is not set, the package signs tokens with the hard-coded key 'auth-secret-key'. Because that key is public, an attacker can sign their own tokens containing any user ID. The populateContextFromToken function accepts those tokens, which gives the attacker the identity of whichever user they chose. The record lists the weakness as CWE-1394.

Why It Matters

VulnCheck rates the flaw CRITICAL: CVSS 3.1 base score 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and CVSS 4.0 base score 9.3. The attack works over the network, has low complexity, and needs no privileges or user interaction. A successful attacker can impersonate any account, including administrators. Confidentiality, integrity, and availability impacts are all rated high.

There is no CISA KEV entry for this CVE, so active exploitation is not confirmed. CISA's SSVC assessment rates exploitation "none", automatable "yes", and technical impact "total". Even without known exploitation, the key is public and the attack can be automated, so exposed deployments are at serious risk.

What's Vulnerable

The vulnerable code path is referenced in packages/auth/src/index.ts (lines 94–98) of the Tensei repository.

Patch Status

The supplied NVD and vendor data do not name a fixed version. NVD status is "Received" (published 2026-11-16). The record lists no CISA KEV required action or due date.

The flaw only occurs when JWT_SECRET is unset. Operators running @tensei/auth 0.11.5 or earlier should check that every deployment sets JWT_SECRET explicitly. They should also follow the GitHub issue and the VulnCheck advisory for any upstream fix.

Sources