CVE-2026-27629
Inventree Project Inventree ≤ 1.2.3
Raw vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:LSummary
CVE-2026-27629 is a medium-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Inventree Project Inventree. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-27629 affects InvenTree, an open source inventory management system, in versions prior to 1.2.3. The vulnerability stems from insecure server-side Jinja2 templates used for generating custom batch codes. These templates are customizable and can be modified by users with staff permissions, allowing injection of malicious code that exposes sensitive server information to clients or enables server-side code execution. The issue is rated with a CVSS v3.1 base score of 5.9 (AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) and is associated with CWE-1336.
Exploitation requires initial access by a user with staff permissions to modify the batch code template maliciously. Subsequently, any user can trigger the vulnerability by making an API request to generate a custom batch code, causing the tampered template to execute in the context of the requesting user's permissions. Attackers can achieve exfiltration of sensitive information or arbitrary code execution on the server, though it demands adjacent network access, low attack complexity, low privileges, and user interaction.
The vulnerability has been patched in InvenTree version 1.2.3 and all versions from 1.3.0 onward, with template generation now restricted to a secure sandboxed context. Advisories recommend upgrading immediately. As a workaround for unpatched installations, system administrators can override the STOCK_BATCH_CODE_TEMPLATE and PART_NAME_FORMAT global settings at the system level to prevent client-side editing; this requires server access and cannot be altered post-deployment. Details are available in the GitHub Security Advisory at https://github.com/inventree/InvenTree/security/advisories/GHSA-cx85-vr3q-9x4m.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8602
Vulnerability Data
InvenTree is an Open Source Inventory Management System. Prior to version 1.2.3, insecure server-side templates can be hijacked to expose secure information to the client. When generating custom batch codes, the InvenTree server makes use of a customizable jinja2 template,…
more
which can be modified by a staff user to exfiltrate sensitive information or perform code execution on the server. This issue requires access by a user with granted staff permissions, followed by a request to generate a custom batch code via the API. Once the template has been modified in a malicious manner, the API call to generate a new batch code could be made by other users, and the template code will be executed with their user context. The code has been patched to ensure that all template generation is performed within a secure sandboxed context. This issue has been addressed in version 1.2.3, and any versions from 1.3.0 onwards. Some workarounds are available. The batch code template is a configurable global setting which can be adjusted via any user with staff access. To prevent this setting from being edited, it can be overridden at a system level to a default value, preventing it from being edited. This requires system administrator access, and cannot be changed from the client side once the server is running. It is recommended that for InvenTree installations prior to 1.2.3 the `STOCK_BATCH_CODE_TEMPLATE` and `PART_NAME_FORMAT` global settings are overridden at the system level to prevent editing.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.2V1.3.7V1.3.10
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis can discover missing neutralization of template directives.
Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.
Security engineering principles require use of safe templating APIs and proper escaping of external input.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper input neutralization in template engines to prevent injection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect template-injection flaws but does not itself implement neutralization controls.
Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.
Application security requirements explicitly call for neutralizing special elements in template engines.
Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.
Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.