Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Tensei Auth Default JWT Secret Bypass (CVE-2026-129552)

CVE-2026-129552 is a conditional authentication bypass in Tensei's @tensei/auth package through version 0.11.5.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-129552
Vendor
Tensei
Affected Product
@tensei/auth
Exploitation
Not confirmed
Published
2026-11-16

VulnCheck says the package falls back to a hard-coded JWT signing key when JWT_SECRET is unset. A deployment with a separate, configured signing secret does not meet that stated condition.VulnCheck says an unauthenticated attacker could sign a token for an arbitrary user ID. The token is accepted by populateContextFromToken, allowing impersonation of that user, including an administrator. This describes a potential path to unauthorized access, not a confirmed incident.

What it allows

How Does CVE-2026-129552 Bypass Tensei Authentication?

JWT verification depends on the server's signing key. VulnCheck reports that @tensei/auth uses a fixed fallback key if the JWT_SECRET environment variable is missing. In that configuration, knowledge of the fallback lets an unauthenticated actor create a token the application may accept.

The advisory says populateContextFromToken accepts a signed token containing an arbitrary user ID. That means the actor could impersonate an existing account, including an administrator, if the affected application trusts the token. The exposed condition is the missing environment variable, so inventory must check configuration as well as package version.

What Does the Available Evidence Say About Risk?

VulnCheck rates the issue Critical. Brandefense Blackhole counted one dark-chat post mentioning CVE-2026-129552 from 18 August through 16 November 2026. The measured unit is a post, and that observation does not establish exploitation or an affected deployment.

The CISA KEV catalog version dated 13 November 2026 did not list this CVE. Because the CVE was published on 16 November, that earlier catalog snapshot cannot resolve its present exploitation status. Treat a missing JWT_SECRET on an exposed application as the priority condition regardless of discussion volume.

Use a vulnerability intelligence platform to track the advisory and configuration decisions. The vulnerability intelligence glossary explains how to distinguish an observed signal from a confirmed incident.

Who is affected

Which Tensei Installations Are Affected by CVE-2026-129552?

VulnCheck names @tensei/auth versions through 0.11.5. Exposure requires JWT_SECRET to be unset, causing the package to use its fixed fallback signing key. NVD had not analyzed product configurations when its record was captured on 16 November 2026.

Inventory applications that load @tensei/auth and check the running package version. Inspect each deployment's effective JWT_SECRET configuration without recording the secret value in a ticket or log. A package version alone does not prove the unsafe fallback is in use.

The opened advisory does not identify a fixed release, so this profile does not supply a machine-readable version range or claim a particular upgrade resolves the flaw. Track any future vendor release through the patch management process, and verify the running version and effective configuration after deployment.

Timeline

  1. 2026-11-13

    CISA KEV catalog version 2026.11.13 did not include CVE-2026-129552.

  2. 2026-11-16

    VulnCheck published its advisory; NVD published the CVE record on the same day.

What to do

  1. Inventory the package and configuration

    Find applications running @tensei/auth through 0.11.5. Confirm whether JWT_SECRET is configured in the effective runtime environment, and record only its presence, not its value.

  2. Replace the fallback signing key

    For affected deployments, set a unique, unpredictable JWT_SECRET through the approved secret manager and restart or redeploy the application. Rotate any signing secret shared across environments and invalidate existing sessions where supported. These are defensive recommendations based on the disclosed fallback condition.

  3. Review suspicious account activity

    For deployments that used the fallback, review authentication and administrator activity for unexpected sessions or changes. Investigate anomalous activity through the normal incident process; a chat mention alone is not proof of compromise.

  4. Verify remediation and future release

    Confirm the running application loads the intended secret after restart and no longer takes the fallback path. When Tensei documents a fixed version, update the package, verify that version at runtime, and retest the configuration before closing the issue.

What Brandefense can do

Frequently Asked Questions

Does CVE-2026-129552 affect every Tensei installation?

No. VulnCheck describes @tensei/auth through 0.11.5 when JWT_SECRET is unset. Check both the loaded package version and the effective runtime setting.

Can CVE-2026-129552 impersonate an administrator?

VulnCheck says an unauthenticated actor could sign a token for an arbitrary user ID. If the application accepts it, that can include an administrator account.

Which @tensei/auth release fixes CVE-2026-129552?

The opened VulnCheck advisory identifies versions through 0.11.5 as affected but does not identify a fixed release. Verify any later vendor update before treating an upgrade as a fix.

What should teams check first?

Find deployments with @tensei/auth through 0.11.5 and determine whether JWT_SECRET is set at runtime. Prioritize reachable installations using the fallback, then change the secret and investigate suspicious sessions.

Sources

  1. Tensei through 0.11.5 Authentication Bypass via Hard-Coded JWT SecretVulnCheck
  2. CVE-2026-129552 DetailNVD
  3. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →