Is this vulnerability remotely exploitable?

Yes. Any user who can remotely authenticate to the InvenTree API can exploit this issue by calling the token-creation endpoint with another user's ID. Once obtained, the forged token can be used from any network location.

Does this require administrator or special privileges?

No. The vulnerability can be exploited by any authenticated user, including low-privileged accounts, because the API does not properly restrict which user IDs can be associated with newly created tokens.

What is the safest general fix pattern?

The safest approach is to derive token ownership exclusively from the authenticated session and disallow arbitrary selection of a different user account. If administrative token creation is required, wrap it in explicit role checks and limit it to designated administrator roles.

Severity:

HIGH RISK

(8.3)

Improper Authorization for User Token Creation (CWE-639) in InvenTree API

CVE-2026-35478

Published:

Apr 8, 2026

Status:

Undergoing Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI Handler setAccessDeviceCfg

Remote Code Execution on the Router

April 12, 2026

CWE-77;CWE-78

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI setLedCfg Handler

Remote Code Execution on the Router

April 12, 2026

Vulnerability Type

Category:

Improper Authorization

CWE:

CWE-639

Impact:

Authentication Bypass and Privilege Escalation via Token Impersonation

Severity:

HIGH RISK

(8.3)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Authorization

CWE:

CWE-639

Impact:

Authentication Bypass and Privilege Escalation via Token Impersonation

Severity:

HIGH RISK

(8.3)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Improper Authorization for User Token Creation (CWE-639) in InvenTree API

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI Handler setAccessDeviceCfg

CRITICAL RISK

CRITICAL

(9.8)

OS Command Injection (CWE-78) in Totolink A7100RU CGI setLedCfg Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare