External risk intelligence

InvenTree Staff Privileges Code Execution Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-35477

InvenTree is an inventory management system typically deployed as a web application. While this specific vulnerability requires authenticated staff access, the product itself is designed as a web-based service often exposed to the network or internet to allow authorized users to manage inventory, making it a likely candidate for public or wide-area network exposure in common deployments.

Inventree Project Inventree

1.2.3 to 1.2.6

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability in InvenTree, an open-source inventory management system. The issue allows a privileged user to execute arbitrary code by crafting a malicious template, potentially leading to a full system compromise. The vulnerability is present in specific versions of InvenTree and has been fixed in later releases.

A system flaw allows code execution with staff access.
Protects sensitive inventory and operational data.
Confirm InvenTree version relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker with staff-level access within InvenTree can craft a malicious template designed to bypass validation checks. When this template is rendered for use, it can lead to arbitrary code execution.

Authenticated staff user required.
Malicious template passed validation.
Arbitrary code execution possible.

Live Threat

Current exploitation, exposure, and threat context

A staff user with settings access could craft a malicious template. When this template is rendered, it could lead to the execution of arbitrary code on the server, affecting the integrity and availability of the inventory management system.

Server-side code execution.
Crafted template rendered by staff.
Compromise of system data and behavior.

Operational Fix

Recommended remediation, mitigation, and detection steps

To address this vulnerability, the InvenTree application owners and their respective infrastructure or platform teams are likely responsible for remediation. The first practical step is to identify all InvenTree instances, confirm their reachability and business criticality, and then coordinate with the accountable owners to plan remediation actions, such as upgrading the software.

Application owners should manage the issue.
Verify all InvenTree instances are identified.
Plan upgrade during maintenance window.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is InvenTree used for?

InvenTree is an open-source inventory management system designed to track parts, stock levels, and manufacturing workflows. It functions as a web-based application, allowing organizations to maintain visibility into their physical assets and internal operational data through a centralized interface.

What does CWE-1336 mean for CVE-2026-35477?

CWE-1336 refers to the improper neutralization of special elements in template engines. In this context, it means the software's template rendering system fails to adequately separate user-supplied input from the underlying execution environment. Because the application uses an insecure, non-sandboxed environment to process templates, an attacker can input code that the system mistakenly runs as a legitimate command.

How can a user trigger this vulnerability?

The flaw is triggered when a staff-level user with settings access inputs a malicious template. Validation checks do not prevent this because they use a limited, dummy instance that behaves differently than the actual production renderer. Simply browsing or using standard inventory features does not trigger the bug; it requires an active, intentional attempt to submit a crafted template string that bypasses those initial validation gates.

Is my InvenTree instance at risk according to Halo Surface Signal?

Halo Surface Signal identifies InvenTree as a web-based service frequently exposed to networks or the internet to support remote inventory management. Because it is designed to be accessible to authorized users, any instance reachable over a wide-area network or the public internet is considered a likely candidate for exposure, increasing the priority of monitoring and securing staff accounts.

What should I do to secure my software?

First, verify which version of InvenTree you are currently running. If you are on any version between 1.2.3 and 1.2.6, you should plan an update to version 1.2.7 or 1.3.0, where the renderer has been correctly updated to use a secure, sandboxed environment. Coordinate with your team to schedule this upgrade during a maintenance window to mitigate the risk of arbitrary code execution.

References

github.com/inventree/InvenTree/security/advisories/GHSA-84jh-x77…

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.