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.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Default setups
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.
Written by a model
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”
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"}.Affected versions
cve.now Index
- 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
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Public exploit activity
- EPSS: 0.40%
- Posted on X by cve.now Nov 16
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129550 |
| Record | NVD · CVE-2026-129550 |
| Other links 4 | |
| Report | GitHub · tenseijs/tensei · Issue #398 |
| Repository | GitHub · tenseijs/tensei · packages/auth/src/index.ts · L311-L333 |
| Repository | GitHub · tenseijs/tensei · Repository |
| Link | vulncheck.com · advisories/tensei-through-0.11.5-privilege-escalation-via-self-assigned-roles-in-tensei-auth |
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
Related
- CVE-2026-129552Tensei through 0.11.5 Authentication Bypass via Hard-Coded JWT Secret in @tensei/auth
- CVE-2026-129551Tensei through 0.11.5 Unauthenticated Prototype Pollution via sort Parameter
- CVE-2026-129549Tensei through 0.11.5 Unauthenticated File Upload via @tensei/media files/upload
- CVE-2026-129553Tensei through 0.11.5 Open Redirect via @tensei/social-auth OAuth Callback
- CVE-2026-134169Qwik City before 1.20.3 and Router before 2.0.0-rc.4 DoS via formToObj
- CVE-2026-129874REBUILD 3.5.0 through 4.5.4 Privilege Escalation via roleId Mass Assignment
No corrections so far. Something wrong on this page? Report an error.