⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 5.9

How to Fix CVE-2026-27629: Improper neutralization of special elements used in a template engine in InvenTree

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-27629 is a improper neutralization of special elements used in a template engine in inventree InvenTree. The fix is to apply the vendor patch noted below.

⚡ At a glance
Severity5.9 (Medium)
Actively exploited?No public listing in CISA KEV
AffectedInvenTree < 1.2.3
Fixed inSee vendor advisory
Type (CWE)CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine

What is CVE-2026-27629?

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, 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. The CVSS base score is 5.9 (Medium). The official advisory is at https://github.com/inventree/InvenTree/security/advisories/GHSA-cx85-vr3q-9x4m.

Am I affected?

Check the version of InvenTree you are running and compare it against the Affected row above (InvenTree < 1.2.3). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s inventree 2>/dev/null | grep -i ^Version
rpm -q inventree 2>/dev/null
command -v inventree >/dev/null && inventree --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*InvenTree*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "InvenTree" 2>$null

How to fix CVE-2026-27629

Upgrade InvenTree to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade inventree
dpkg -s inventree | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh inventree -y
# or for older releases:
sudo yum update inventree -y
rpm -q inventree

SUSE / openSUSE


sudo zypper refresh
sudo zypper update inventree
rpm -q inventree

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-27629 affecting InvenTree
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27629-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*InvenTree*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\inventree-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\InvenTree" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "InvenTree" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "InvenTree"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-27629 affecting InvenTree
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27629-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s inventree 2>/dev/null | grep -i ^Version || echo "inventree not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q inventree || echo "inventree not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27629-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/inventree /etc/inventree.d /etc/inventree.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y inventree
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y inventree
elif command -v yum >/dev/null; then
    yum update -y inventree
elif command -v zypper >/dev/null; then
    zypper --non-interactive update inventree
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s inventree 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q inventree
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-27629" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27629"

Disable the affected service (Linux)


sudo systemctl stop inventree 2>/dev/null || true
sudo systemctl disable inventree 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s inventree 2>/dev/null | grep -i ^Version
rpm -q inventree 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*InvenTree*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-27629 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-27629?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-27629?

5.9 (Medium). Vector: CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L.

Where is the official advisory for CVE-2026-27629?

The vendor advisory is at https://github.com/inventree/InvenTree/security/advisories/GHSA-cx85-vr3q-9x4m. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27629.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*