# CVE-2026-35477: InvenTree has SSTI in PART_NAME_FORMAT bypasses CVE-2026-27629 fix via {% if part.pk %} sandbox escape

> A staff user can execute arbitrary code via Server-Side Template Injection in InvenTree due to inconsistent sandboxing between validation and rendering.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-84jh-x777-8pqq

## What is CVE-2026-35477?

CVE-2026-35477 is a medium-severity code injection vulnerability in InvenTree, published on 8 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-35477?

It affects 1 product.


Products: Inventree Project Inventree.

## How do I fix CVE-2026-35477?

No fix has been published for CVE-2026-35477 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35477 being exploited?

There is no known exploitation of CVE-2026-35477 in the wild and no public exploit code.

## Other vulnerabilities in InvenTree

- [CVE-2022-2111](https://insights.sbomify.com/CVE-2022-2111/): Unrestricted Upload of File with Dangerous Type in inventree/inventree (critical 9.0)
- [CVE-2022-2112](https://insights.sbomify.com/CVE-2022-2112/): Improper Neutralization of Formula Elements in a CSV File in inventree/inventree (critical 9.0)
- [CVE-2022-2113](https://insights.sbomify.com/CVE-2022-2113/): Cross-site Scripting (XSS) - Stored in inventree/inventree (high 8.4)
- [CVE-2026-35478](https://insights.sbomify.com/CVE-2026-35478/): InvenTree has Arbitrary API Token Creation (high 8.3)
- [CVE-2022-3355](https://insights.sbomify.com/CVE-2022-3355/): Cross-site Scripting (XSS) - Stored in inventree/inventree (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35477 and fix it if it is affected.

What it is: CVE-2026-35477 is a medium-severity code injection vulnerability in InvenTree, published on 8 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35477 in the wild and no public exploit code.

Affected product: InvenTree. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35477/ (Markdown: https://insights.sbomify.com/CVE-2026-35477/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35477
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35477
- OSV: https://osv.dev/vulnerability/CVE-2026-35477

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35477/
Summaries are generated and may contain mistakes; the official description above is the record.