CVE-2026-129552 Tensei through 0.11.5 Authentication Bypass via Hard-Coded JWT Secret in @tensei/auth

Critical 9.3 Published Updated

When JWT_SECRET is unset, attackers can forge tokens with any user id to impersonate any user, including admins, in apps using Tensei auth.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Harmful if only installed
Yes
Needs a specific call
No
Fix
None listed

What is CVE-2026-129552?

CVE-2026-129552 is a critical hardcoded credentials vulnerability in tenseijs @tensei/auth, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-1394

Which versions are affected by CVE-2026-129552?

1 open source package ship an affected version, including @tensei/auth.

Having an affected version installed is enough. The problem is in what it ships or how it installs, so no code has to call it.

PackageAffectedFixed in
@tensei/auth npm
pkg:npm/%40tensei/auth
All versions to 0.11.5None

How do I fix CVE-2026-129552?

No fix has been published for CVE-2026-129552 yet. Limit exposure of the affected software until one is available.

Upgrade, then change or revoke the exposed credential wherever it is used. More about Hardcoded credentials.

Is CVE-2026-129552 being exploited?

There is no known exploitation of CVE-2026-129552 in the wild and no public exploit code.

Sources

Also known as GHSA-2q55-g3jv-fgmf.

Is CVE-2026-129552 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free