CVE-2026-35478
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInvenTree is an Open Source Inventory Management System. From 0.16.0 to before 1.2.7, any authenticated InvenTree user can create a valid API token attributed to any other user in the system — including administrators and superusers — by supplying the target's user ID in the user field of a POST /api/user/tokens/ request. The returned token is immediately usable for full API authentication as the target user, from any network location, with no further interaction required. This vulnerability is fixed in 1.2.7 and 1.3.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInvenTree versions 0.16.0 through 1.2.6 contain a broken access control vulnerability in the /api/user/tokens/ endpoint. Any authenticated user can create API tokens for arbitrary users by supplying a target user ID in the POST request, enabling complete account takeover of the targeted user including administrators.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 0.16.0, <= 1.2.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify InvenTree versionLocate the installed InvenTree version by checking the admin interface footer, the 'about' page, or the version file in the installation directory. Compare this version number against the affected range 0.16.0 to 1.2.6.Affected if The installed version falls within 0.16.0 through 1.2.6
-
Confirm /api/user/tokens/ endpoint is exposedAttempt to access the /api/user/tokens/ endpoint using a web browser or curl with valid authentication credentials (any valid user account). A successful HTTP 200 response indicates the endpoint exists and is accessible.Affected if The endpoint responds with HTTP 200 and returns token listing or creation forms
-
Test IDOR vulnerability with non-admin accountUsing a low-privilege authenticated user account, send a POST request to /api/user/tokens/ that includes a different user ID in the request body (for example, targeting an administrator or superuser account). Check if the API accepts this request and creates a token for the target user.Affected if A non-admin user can successfully create an API token for a different user by specifying that user's ID in the request
-
Verify unauthorized token creation capabilityIf step 3 succeeds, list the tokens for the target user account (or inspect the created token) to confirm the token was actually created for the target user rather than the requesting user. This confirms the IDOR flaw allows cross-user token creation.Affected if Tokens appear in a different user's account that were created by a non-admin user
A user is affected if their InvenTree installation runs version 0.16.0 through 1.2.6 and the /api/user/tokens/ endpoint permits authenticated users to create API tokens for other users by specifying a target user ID in POST requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to InvenTree 1.2.7 or 1.3.0 which enforce proper authorization checks ensuring users can only create tokens for their own account. Additionally, audit existing API tokens and logs for suspicious activity.
1.2.7 or 1.3.0 (both contain the fix)
- Upgrade InvenTree to version 1.2.7 or 1.3.0 to resolve the IDOR vulnerability
- Review the InvenTree release notes for version 1.2.7 and 1.3.0 for any required migration steps or configuration changes
- After upgrading, verify that regular users can no longer create API tokens for other users via POST /api/user/tokens/
- If any suspicious tokens exist for users other than the requester, revoke them immediately via the admin interface
- Ensure your deployment follows InvenTree's recommended security practices for API token management
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35478 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35478 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data