Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 20 Apr 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Inventree Project
Inventree Project inventree |
|
| CPEs | cpe:2.3:a:inventree_project:inventree:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Inventree Project
Inventree Project inventree |
Fri, 10 Apr 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 09 Apr 2026 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Inventree
Inventree inventree |
|
| Vendors & Products |
Inventree
Inventree inventree |
Wed, 08 Apr 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | InvenTree is an Open Source Inventory Management System. From 1.2.3 to 1.2.6, the fix for CVE-2026-27629 upgraded the PART_NAME_FORMAT validator to use jinja2.sandbox.SandboxedEnvironment. However, the actual renderer in part/helpers.py was not updated and still uses the non-sandboxed jinja2.Environment. Additionally, the validator uses a dummy Part instance with pk=None, which allows conditional template expressions to behave differently during validation versus production rendering. A staff user with settings access can craft a template that passes validation but executes arbitrary code during rendering. This issue requires access by a user with granted staff permissions. This vulnerability is fixed in 1.2.7 and 1.3.0. | |
| Title | InvenTree has SSTI in PART_NAME_FORMAT bypasses CVE-2026-27629 fix via {% if part.pk %} sandbox escape | |
| Weaknesses | CWE-1336 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-10T20:43:12.243Z
Reserved: 2026-04-02T20:49:44.453Z
Link: CVE-2026-35477
Updated: 2026-04-10T20:43:07.097Z
Status : Analyzed
Published: 2026-04-08T20:16:24.487
Modified: 2026-04-20T15:14:39.303
Link: CVE-2026-35477
No data.
OpenCVE Enrichment
Updated: 2026-04-09T08:27:43Z