CVE-2026-33530 InvenTree Vulnerable to ORM Filter Injection

High 7.7 Published 26 Mar 2026 Updated 30 Mar 2026

Authenticated users can exploit unvalidated ORM filters in InvenTree API endpoints to extract sensitive database information via blind boolean-based injection.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2026-33530?

CVE-2026-33530 is a high-severity SQL injection 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, certain API endpoints associated with bulk data operations can be hijacked to exfiltrate sensitive information from the database. The bulk operation API endpoints (e.g. `/api/part/`, `/api/stock/`, `/api/order/so/allocation/`, and others) accept a filters parameter that is passed directly to Django's ORM queryset.filter(**filters) without any field allowlisting. This enables any authenticated user to traverse model relationships using Django's __ lookup syntax and perform blind boolean-based data extraction. 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-202

Which versions are affected by CVE-2026-33530?

It affects 1 product.

Products include Inventree Project Inventree.

How do I fix CVE-2026-33530?

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

Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.

Is CVE-2026-33530 being exploited?

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

Sources

Also known as GHSA-m8j2-vfmq-p6qg.