# CVE-2026-33531: InvenTree has Path Traversal In Report Templates

> A staff-level user can read arbitrary files from the server filesystem via crafted report template tags in InvenTree.

- **Severity:** Medium 4.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-rhc5-7c3r-c769

## What is CVE-2026-33531?

CVE-2026-33531 is a medium-severity path traversal vulnerability in InvenTree, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

InvenTree is an Open Source Inventory Management System. Prior to version 1.2.6, a path traversal vulnerability in the report template engine allows a staff-level user to read arbitrary files from the server filesystem via crafted template tags. Affected functions: `encode_svg_image()`, `asset()`, and `uploaded_image()` in `src/backend/InvenTree/report/templatetags/report.py`. This requires staff access (to upload / edit templates with maliciously crafted tags). If the InvenTree installation is configured with high access privileges on the host system, this path traversal may allow file access outside of the InvenTree source directory. This issue is patched in version 1.2.6, and 1.3.0 (or above). Users should update to the patched versions. No known workarounds are available.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Inventree Project Inventree.

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

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

## Is CVE-2026-33531 being exploited?

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

Public exploit code:

- This repository contains a professional write-up of a path traversal vulnerability discovered in InvenTree's report template engine. This vulnerability was patched in versions 1.2.6 and 1.3.0. (github_poc): https://github.com/alonaki/InvenTree-Path-Traversal-CVE-2026-33531

## 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-33531 and fix it if it is affected.

What it is: CVE-2026-33531 is a medium-severity path traversal vulnerability in InvenTree, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33531 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-33531/ (Markdown: https://insights.sbomify.com/CVE-2026-33531/index.md)
```

## Sources

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

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