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

An attacker exploiting this vulnerability could gain complete control over the InvenTree server. By crafting a specially designed template, a malicious staff user could execute arbitrary system commands, potentially leading to data breaches, system compromise, and denial of service. The impact is particularly severe as it allows for remote code execution without requiring complex exploits or specialized knowledge, making it accessible to a wider range of attackers. This vulnerability shares similarities with other template injection flaws where insufficient sandboxing allows for code execution.

Organizations utilizing InvenTree for inventory management, particularly those running vulnerable versions (1.2.3 - 1.2.6) in production environments, are at risk. Shared hosting environments where InvenTree is deployed alongside other applications are also vulnerable, as a compromise of one application could lead to the exploitation of this vulnerability.

• python / server:

import os
import subprocess

def check_invenTree_version():
    try:
        result = subprocess.check_output(['pip3', 'show', 'invenTree'], stderr=subprocess.STDOUT)
        version = result.decode('utf-8').split('Version: ')[1].strip()
        if '1.2.3' <= version < '1.2.7':
            print("VULNERABLE: InvenTree version detected.")
        else:
            print("InvenTree version is not vulnerable.")
    except FileNotFoundError:
        print("InvenTree not found.")
    except Exception as e:
        print(f"Error checking version: {e}")

check_invenTree_version()

• generic web:

curl -I http://your-invenTree-instance/admin/settings/ | grep -i 'jinja2'

1. 2026-04-08Disclosure

   disclosure

1. आरक्षित2026-04-02
2. प्रकाशित2026-04-08
3. संशोधित2026-04-10
4. EPSS अद्यतन2026-04-16

The primary mitigation for CVE-2026-35477 is to immediately upgrade InvenTree to version 1.2.7 or later. If upgrading is not immediately feasible, consider restricting access to settings modification for staff users to only trusted personnel. Implement strict input validation and sanitization for all user-supplied data, particularly template inputs. While a WAF might offer some protection, it's unlikely to be effective against this type of template injection without specific, custom rules. After upgrading, verify the fix by attempting to render a template with potentially malicious code to ensure it is properly sandboxed.