Skip to main content
Menu
CVEs

CVE

Tensei Auth privilege escalation via self-assigned roles

@tensei/auth through 0.11.5 lets users assign themselves arbitrary roles, including administrator, because the Roles field is exposed on the user update API. No fixed version is listed.

CVE-2026-129550EUVD-2026-126284GHSA-3WRX-9CQF-R3HH

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

9.3CriticalCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Default setups

Do first: Check every install: default setups are affected.

Published
Last modified
Reference
Last checked
50/100 · provisional
Default setups
100% of @tensei/auth downloads last week were affected versions (70).npm, 70 downloads in the last 7 days, read Nov 16, 2026
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: yes
  • Technical impact: total

Summary

Tensei through 0.11.5 has a flaw in the @tensei/auth package that lets users give themselves any role, including administrator. An attacker can do this remotely, without logging in, by including a roles array when registering, posting to the users route, or patching their own record.

Original description

Tensei through 0.11.5 contains a privilege escalation vulnerability in @tensei/auth that allows unauthenticated or authenticated users to assign themselves arbitrary roles via the exposed User Roles field. Attackers can supply a roles array during registration, a POST to the users route, or a PATCH to their own record to gain administrator permissions.

Who should check

Teams running @tensei/auth 0.11.5 or earlier in Tensei apps that expose user roles through registration, the users route or self-update.

“Affecting @tensei/auth <= 0.11.5”

vulncheck.com

cve.now Index

50Pcve.now Index 50 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure25/25Default setups, CISA rates it automatable
  • Reach10/20Affects npm packages
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 90 if added to CISA KEV
  • Would score about 85 if CISA's SSVC rates exploitation active

Impact

  • Widely used

    @tensei/auth has 70 weekly downloads.Source: npmjs.com

    5 packages depend on @tensei/auth.Source: deps.dev

What to do

  • Check every install: default setups are affected.

  • Workaround: The checked facts name no workaround or mitigation for this vulnerability.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129550 (Tensei through 0.11.5 Privilege Escalation via Self-Assigned Roles 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-129550 (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):
- Affects @tensei/auth through 0.11.5 (source: https://www.vulncheck.com/advisories/tensei-through-0.11.5-privilege-escalation-via-self-assigned-roles-in-tensei-auth)
- The Roles field is exposed on the user update API (source: https://github.com/tenseijs/tensei/issues/398)
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-129550 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129550 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#L311-L333
- https://github.com/tenseijs/tensei
- https://www.vulncheck.com/advisories/tensei-through-0.11.5-privilege-escalation-via-self-assigned-roles-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-129550
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-129550"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Affected versions

  • through 0.11.5

    No fix released. The latest release, 0.11.5, is still affected.

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Report
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129550

Is CVE-2026-129550 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: cve.now feed data

What does this mean?

The bug lets a user assign themselves arbitrary roles, including administrator permissions, because the Roles field is exposed on the user update API.Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-129550?

@tensei/auth (npm): through 0.11.5.Source: cve.now feed data

Am I affected, and how do I check?

The product is @tensei/auth, with all versions through 0.11.5 listed as affected. To check an installed copy, look at its @tensei/auth version in the package manifest or lockfile and see whether it is 0.11.5 or earlier.Source: vulncheck.com, github.com

How do I fix CVE-2026-129550?

The checked facts name no fixed version and no vendor patch IDs, so no upgrade target can be given from them.Source: vulncheck.com, github.com

What if there's no patch?

The checked facts name no workaround or mitigation for this vulnerability.Source: vulncheck.com, github.com