{"id":"CVE-2026-129550","kind":"vulnerability","aliases":["CVE-2026-129550"],"related":[],"title":"Tensei: anyone can grant themselves administrator roles via user fields","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.","summary":"Tensei's @tensei/auth package exposes the User Roles field, so a registering or logged-in user can send a roles array and make their own account an administrator. An attacker who gets administrator permissions can read and change the data the Tensei app manages.","severity":"critical","cvss":9.3,"epss":null,"exploited":false,"exploited_at":null,"products":[{"name":"@tensei/auth","fixed":[],"affected":"<= 0.11.5","ecosystem":"npm"}],"ecosystems":[],"tags":["@tensei/auth","node","npm","package","privilege-escalation","self-hosted","tensei"],"not_affected_if":["no-tensei-deployment","roles-field-not-exposed"],"how_to_check":"- Run npm ls @tensei/auth, or look in package-lock.json, yarn.lock or pnpm-lock.yaml. Any version up to 0.11.5 is affected, and 0.11.5 is the latest published.\n- Check that auth() from @tensei/auth is in your tensei().plugins([...]).\n- On a test instance, register or PATCH your own user with a roles array in the body. If the response or database shows the roles were set, you are exposed.\n- Look for accounts that have admin roles and that you did not grant.","fix":"No fixed version is published. The reporter's issue #398 (opened 2026-11-15) is still open with no maintainer reply, and npm lists @tensei/auth 0.11.5 as the latest release. Until a fix ships, do not expose the Roles field to self-service routes. Strip or ignore roles in request bodies on registration, POST /users and self-PATCH, for example in a server-side middleware, and set explicit canUpdate/canCreate rules.","status":"open","published_at":"2026-11-16T12:17:53+00:00","first_seen_at":"2026-11-16T12:40:57+00:00","triaged_at":"2026-11-16T12:42:33+00:00","updated_at":"2026-11-16T12:43:54+00:00","category":"package","confidence":0.8,"triage":{"at":"2026-11-16T12:42:33Z","model":"claude-haiku-5-5","output":{"fix":"unknown","reach":"internet","title":"Tensei: anyone can grant themselves administrator roles via user fields","impact":"high","summary":"Tensei's @tensei/auth package exposes the User Roles field, so a registering or logged-in user can send a roles array and make their own account an administrator. An attacker who gets administrator permissions can read and change the data the Tensei app manages.","audience":"developers","category":"package","nicknames":[],"who_cares":["tensei","@tensei/auth","node","self-hosted"],"confidence":0.7,"fix_status":"unknown","needs_auth":"no","worst_case":"Attacker becomes administrator and reads or changes all app data","analyst_note":"Find the fixed version of @tensei/auth from the Tensei repository or the vulncheck advisory; the sources give no fixed version.","how_to_check":"- Check the installed version of `@tensei/auth` in the project's lockfile or with `npm ls @tensei/auth`\n- Confirm whether `@tensei/auth` is installed in the project at all\n- Check whether registration or the users route accepts a `roles` field in requests","plain_action":"","product_name":"","needs_analyst":true,"not_affected_if":["no-tensei-deployment","roles-field-not-exposed"],"who_is_affected":"Applications built on Tensei through version 0.11.5 that use the @tensei/auth package with its User Roles field exposed are affected. The sources say registration, the users route and self-PATCH are all reachable, so any deployment exposing those endpoints to users is at risk.","user_interaction":"no","product_ecosystem":"","needs_special_setup":"unknown","severity_if_unknown":"critical"},"cost_usd":0.000742,"input_tokens":4598,"output_tokens":565,"severity_before":"critical"},"analyst_status":"done","analyst_note":"Find the fixed version of @tensei/auth from the Tensei repository or the vulncheck advisory; the sources give no fixed version.","search":"'-129550':13A,16A '-2026':12A,15A '0.11.5':76C 'account':55B 'administr':6A,57B,62B,124C 'allow':85C 'anyon':2A 'app':72B 'arbitrari':93C 'array':50B,106C 'assign':91C 'attack':59B,101C 'authent':88C 'chang':67B 'contain':77C 'cve':11A,14A 'data':69B 'escal':24B,80C 'expos':33B,97C 'field':10A,37B,100C 'gain':123C 'get':61B 'grant':4A 'host':27B 'log':43B 'logged-in':42B 'make':52B 'manag':73B 'node':19B 'npm':20B 'packag':21B,32B 'patch':117C 'permiss':63B,125C 'post':110C 'privileg':23B,79C 'privilege-escal':22B 'read':65B 'record':121C 'regist':40B 'registr':108C 'role':7A,36B,49B,94C,99C,105C 'rout':114C 'self':26B 'self-host':25B 'send':47B 'suppli':103C 'tensei':1A,28B,29B,71B,74C 'tensei/auth':17A,18B,31B,83C 'unauthent':86C 'user':9A,35B,45B,89C,98C,113C 'via':8A,95C 'vulner':81C","nicknames":[],"mitigations":[],"who_affected":"Apps built on Tensei that use the @tensei/auth plugin, versions up to 0.11.5 (the latest release). Registration, POST to the users route and a PATCH to your own record are described as accepting a roles array that grants administrator permissions. This comes from the VulnCheck advisory and the reporter's issue. The maintainers have not confirmed it. Apps that do not use @tensei/auth, or that filter the roles field in front of Tensei, can skip it.","tier":"B","verified":{},"analyst_revisit_at":null,"fix_status":"none","audience":"developers","plain_action":null,"pkeys":["auth"],"ptokens":["auth","tensei"],"labels":["auth","critical","node","npm","package","privilegeescalation","selfhosted","tensei"],"campaign_type":null,"search_a":"'-129550':13A,16A '-2026':12A,15A 'administr':6A 'anyon':2A 'cve':11A,14A 'field':10A 'grant':4A 'role':7A 'tensei':1A 'tensei/auth':17A 'user':9A 'via':8A","search_b":"'account':55B 'administr':57B,62B 'app':72B 'array':50B 'attack':59B 'chang':67B 'data':69B 'escal':24B 'expos':33B 'field':37B 'get':61B 'host':27B 'log':43B 'logged-in':42B 'make':52B 'manag':73B 'node':19B 'npm':20B 'packag':21B,32B 'permiss':63B 'privileg':23B 'privilege-escal':22B 'read':65B 'regist':40B 'role':36B,49B 'self':26B 'self-host':25B 'send':47B 'tensei':28B,29B,71B 'tensei/auth':18B,31B 'user':35B,45B","search_c":"'0.11.5':76C 'administr':124C 'allow':85C 'arbitrari':93C 'array':106C 'assign':91C 'attack':101C 'authent':88C 'contain':77C 'escal':80C 'expos':97C 'field':100C 'gain':123C 'patch':117C 'permiss':125C 'post':110C 'privileg':79C 'record':121C 'registr':108C 'role':94C,99C,105C 'rout':114C 'suppli':103C 'tensei':74C 'tensei/auth':83C 'unauthent':86C 'user':89C,98C,113C 'via':95C 'vulner':81C","cause_entry":null,"cause_path":null,"disclosures_checked_at":null,"first_public_at":"2026-11-16T12:17:53+00:00","kev":null,"cvss_vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"disclosure@vulncheck.com","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-129550","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-129550","severity":null,"published_at":"2026-11-16T12:17:53+00:00","modified_at":"2026-11-16T12:17:53+00:00","first_seen_at":"2026-11-16T12:40:57+00:00","fetched_at":"2026-11-16T12:40:57+00:00","note":null},{"source":"analyst","external_id":"CVE-2026-129550:4107","url":"https://github.com/tenseijs/tensei/issues/398","severity":null,"published_at":"2026-11-16T12:43:54+00:00","modified_at":"2026-11-16T12:43:54+00:00","first_seen_at":"2026-11-16T12:43:54+00:00","fetched_at":"2026-11-16T12:43:54+00:00","note":"Sources are the VulnCheck advisory and GitHub issue #398, which the researcher opened publicly. There is no maintainer response and no fix, and 0.11.5 is the latest. Nothing is verified because there is no vendor page. The same issue also reports unauthenticated media upload, default JWT secrets, a CSRF bypass, operator injection and an open redirect, which may get their own CVEs. No PoC is public and no exploitation is known. The fix and mitigation need rechecking when the maintainers reply.","cites":["https://github.com/tenseijs/tensei/issues/398"]}],"documents":[{"id":169504,"url":"https://www.vulncheck.com/advisories/tensei-through-0.11.5-privilege-escalation-via-self-assigned-roles-in-tensei-auth","title":"Third-party advisory: www.vulncheck.com","kind":"advisory","source":"nvd","publisher":"research","text":null,"published_at":null,"relation":"advisory","confidence":null,"note":"Third-party advisory: www.vulncheck.com"},{"id":169514,"url":"https://github.com/tenseijs/tensei/issues/398","title":"tenseijs/tensei #398: Multiple high-severity vulnerabilities (open, reporter Ikram-4)","kind":"issue","source":"analyst","publisher":null,"text":null,"published_at":null,"relation":"describes","confidence":null,"note":null}],"disclosures":[],"exploit_sources":[],"notice":"Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai"}