# CVE-2026-35478: InvenTree authorization bypass in API token generation

Source: https://junglewise.ai/threats/cve-2026-35478-inventree-authorization-bypass-in-api-token-generation  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-08. Updated: 2026-07-24  
License: CC BY 4.0 with a link back

CVE-2026-35478 · Severity: high · CVSS 8.3 · Published 2026-04-08

InvenTree, an open-source inventory management system, contains a security flaw that allows any logged-in user to impersonate any other user, including administrators. By sending a specifically crafted request, an attacker can generate a secret access key for another person's account. This allows the attacker to view sensitive inventory data, modify records, or take full control of the system as an administrator.

## Quick answers

**Is CVE-2026-35478 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-35478 being exploited in the wild.

**How severe is CVE-2026-35478?** High severity, with a CVSS score of 8.3, published 8 April 2026.

**Which products and versions are affected?** InvenTree InvenTree >= 0.16.0, < 1.2.7.

**Is there a fix for CVE-2026-35478?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-35478 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-35478?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An authorization bypass vulnerability (CWE-639) exists in InvenTree's API token generation endpoint. The root cause is a failure to validate that the authenticated user requesting a token matches the user ID provided in the request body. An attacker with low-level authenticated access can send a POST request to /api/user/tokens/ containing the user ID of a target (such as a superuser). The system then returns a valid API token for that target user. This token can be used immediately for full API authentication from any location without further interaction. The issue is fixed in versions 1.2.7 and 1.3.0.

## Affected products

- InvenTree InvenTree >= 0.16.0, < 1.2.7

## Timeline

- 2026-04-07: advisory: GitHub Security Advisory published
- 2026-04-08: disclosed: CVE published to NVD

## References

- [https://github.com/inventree/InvenTree/security/advisories/GHSA-qh5j-c28q-c4rg](https://github.com/inventree/InvenTree/security/advisories/GHSA-qh5j-c28q-c4rg)