Jekyll2026-11-19T05:48:57+00:00/blog/feed.atomInvenTreeInvenTree is an open-source inventory management system which provides intuitive parts management and stock control. It is at the center of an ecosystem of addins for EDA tools, API wrapper, deeply integrated plugins and 3rd party tools.1.7.0 Release2026-11-03T00:00:00+00:002026-11-03T00:00:00+00:00/blog/2026/11/03/1.7.0InvenTree 1.7.0 has been released! This release includes a critical security fix, a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.

Changelog

Major changes are documented in the CHANGELOG.md file in the repository. For a full list of changes, please refer to the release notes.

Update Procedure

To update to the latest version of InvenTree, please follow the updating instructions provided in the InvenTree documentation. Note that the particular update procedure may vary depending on your installation method.

Security Fixes

This release contains a fix for a critical, low-complexity privilege escalation vulnerability, affecting a range of releases since 2025. Full details, including the associated security advisory, will be published shortly after release — please see our earlier announcement and watch our security advisories page for the disclosure. If you have not already done so, please update to 1.7.0 as a priority.

A number of other security vulnerabilities and hardening improvements are also included in this release.

Security Advisories

The following security advisories have been published in relation to this release:

  • https://github.com/inventree/InvenTree/security/advisories/GHSA-wx67-9cjx-8cr8
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-mw93-g6gp-wvqr
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-q3pw-mh42-p63c
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-vv2m-4hv4-5qr8
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-whr7-8gj9-rqvm
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-m4r7-7rrj-gfm2

CSV Export Formula Injection

PR #13084 sanitizes user-controlled data before it is written into exported CSV files, preventing CSV injection attacks where a crafted cell value could execute a formula when the export is opened in a spreadsheet application. PR #13110 is a follow-up fix which relaxes this escaping for legitimate numeric values.

Report Data Hardening

PR #13111 hardens data access during report generation, excluding sensitive data from the report rendering context and preventing database writes from being triggered as a side effect of generating a report or label.

Session & Token Hardening

Several related fixes tighten up session and API token handling in this release:

  • Revoking an already-revoked token no longer overwrites the original revocation details (PR #13149)
  • Token validity checks now also confirm that the owning user account is still active (PR #13148)
  • Tokens are now masked more securely when displayed, with a fixed lowercase-handling bug and more consistent expiry date checking (PR #13155)
  • Deleting a UserSession via the Django admin interface now also logs out the associated user, rather than leaving the session active (PR #13145)

Additional Hardening

This release also includes routine security-related dependency updates, including CA certificate updates (PR #13057) and a batch of Python dependency security patches (PR #13108).

Breaking Changes

While we strive to maintain backward compatibility, there are some breaking changes in this release. While many of these are minor, and should not affect most users, we recommend that you review the list of breaking changes to ensure that your installation will continue to function as expected after the update. Each breaking change is documented in detail at the links below:

Pricing Model Refactor

PR #13034 moves pricing functionality into a new, dedicated pricing app, with its own API endpoints and a new “pricing” permission role. Existing users with part role permissions automatically retain pricing access via a data migration, laying the groundwork for further pricing improvements in future releases.

Stock Tracking Replaced by Audit Log

PR #13101 removes the legacy “stock item tracking” model and its associated API endpoints, migrating existing entries into the new global audit log introduced in this same release (see “Changelog / Edit History” under New Features, below). The old stock tracking table only ever captured a subset of model changes; the audit log provides a more complete and consistent record. Any external client applications which read stock tracking data via the old API will need to be updated to use the new /api/audit/ endpoints.

New Features

Changelog / Edit History

PR #13069 introduces a global audit log, built on django-auditlog, which tracks changes made to internal data throughout the system. The log is exposed via new read-only /api/audit/ endpoints, and replaces the previous, more limited stock tracking table (see Breaking Changes, above).

Token Issuance Notifications

PR #13141 notifies a user whenever a new API token is issued against their account — whether via the API, the UI, or by an administrator — and separately warns administrators if no email backend is configured, meaning such security alerts cannot be delivered.

Plugin-Launched Forms & Action Context

PR #13174 allows plugins to dynamically launch native modal forms without needing to supply their own React components — for example, triggering a built-in API form from a custom primary action. PR #13172 complements this by passing the current page’s target model and instance ID through to plugin-registered primary actions, giving plugins more context about where they were triggered from.

Stock Adjustment Barcode Actions

PR #13170 implements a number of previously-stubbed stock adjustment actions for barcode scanning, rounding out barcode-driven workflows for adjusting stock.

Default Stock Location from Part

PR #12916 automatically selects the default stock location for a new stock item, if one has been configured against the part being stocked.

Instance Identity Proof for Federation

PR #13030 adds an optional mechanism for an InvenTree instance to cryptographically prove its identity to a federation participant, without exposing its instance ID directly. A time-limited, replayable proof is computed using HKDF and HMAC, and can be requested as an optional parameter on the root API response — early groundwork for future federation work.

Badge Tooltips

PR #13074 adds explanatory tooltips to the status badges shown on detail pages, making it clearer at a glance what each badge represents.

Bug Fixes

As always, we have provided a number of bug fixes with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!

Contributing

InvenTree is an open source project, and we welcome contributions from the community. There are many ways to contribute to the project, including code contributions, translation efforts, documentation improvements, and financial support.

New Contributors

As always we would like to thank all of our contributors for their hard work and dedication to the InvenTree project. In particular, we would like to welcome the following new contributors who have made their first contributions in this release:

  • @Nero7991 made their first contribution in https://github.com/inventree/InvenTree/pull/13100
  • @highvoltagescientist-arch made their first contribution in https://github.com/inventree/InvenTree/pull/13122

Code Contributions

Check out our GitHub page for a list of outstanding issues and feature requests. If you are a developer or want to become one, you can help to contribute to the project by submitting a pull request.

Translation

Our translation efforts continue to grow, with coverage increasing across a wide range of languages. We are grateful to all of our translators who have contributed to making InvenTree accessible to users around the world.

If you are interested in contributing to the translation efforts, please visit our Crowdin project and join the community of translators.

Documentation / Technical Writing

If you have experience with technical writing, you can help to improve the InvenTree documentation. We are always looking for help to improve the documentation and make it more accessible to new users.

Report Bugs

If you encounter a bug in InvenTree, please report it on our GitHub issues page. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.

Financial Contributions

Sponsorships help to keep this project sustainable, and buys time for the core developers to commit to the project. A recurring or one off sponsorship is a great way to help InvenTree development to continue at full steam!

The work undertaken to keep InvenTree running is done by a very small group of core developers, who do so in their spare time (and are not sponsored by their employers to work on InvenTree). If you benefit from the InvenTree project, please consider contributing to maintain vibrant development of this software!

If you are using InvenTree in a commercial setting, please consider sponsoring the project to help support ongoing development and maintenance. Your support is greatly appreciated and helps to ensure that InvenTree remains a viable and sustainable project for years to come.

If your company benefits from InvenTree, please consider a one time sponsorship or a recurring sponsorship to help support the project.

]]>
SchrodingersGat
Action required - Upcoming Security Release2026-11-03T00:00:00+00:002026-11-03T00:00:00+00:00/blog/2026/11/03/security-releaseThe InvenTree core development team has received a report of critical security vulnerabilities affecting a large range of releases since 2025. We will release a disclosure and a fixed release as the part of the 1.7.0 release on 2026-11-03 13:00 UTC.
The vulnerabilities allow known users to privilege escalate within an InvenTree instance. It has a low attack complexity.

Steps to take now

We are not aware of active exploitation of this vulnerability, but we recommend that users take the following steps to mitigate risks:

  • Do not expose your InvenTree instance to the public internet without hardening steps as laid out in the threat model
  • Ensure registration is disabled till the release
  • Ensure you trust all users registered on your instance, especially those with staff or higher permissions

The vulnerabilities have a low complexity and can be expected to be exploited once released. It is important to prepare to update or take your system off the public internet.

Security Policy

As always with security related themes we remind all users, security researchers, and intrested parties of our security policy.

If you have discovered a security vulnerability, please report it to us via the channels described in the policy. We take all reports seriously and will work to address any vulnerabilities in a timely manner.

We would like to thank the security researchers who reported these and several other vulnerabilities in a responsible manner, and we encourage others to do the same in the future. The reporters will be credited in the disclosure and CVE entry.

]]>
matmair
1.6.0 Release2026-10-18T00:00:00+00:002026-10-18T00:00:00+00:00/blog/2026/10/18/1.6.0InvenTree 1.6.0 has been released! This release includes a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.

Changelog

Major changes are documented in the CHANGELOG.md file in the repository. For a full list of changes, please refer to the release notes.

Update Procedure

To update to the latest version of InvenTree, please follow the updating instructions provided in the InvenTree documentation. Note that the particular update procedure may vary depending on your installation method.

Breaking Changes

While we strive to maintain backward compatibility, there are some breaking changes in this release. While many of these are minor, and should not affect most users, we recommend that you review the list of breaking changes to ensure that your installation will continue to function as expected after the update. Each breaking change is documented in detail at the links below:

Notes Refactor

PR #11971 is a major refactor of how notes are handled throughout InvenTree. Notes are now stored in a dedicated table (in line with how attachments and parameters are handled), support multiple separate notes per item, and are accessed via the new /api/note/ endpoint rather than a notes field on individual models. Existing notes data (including embedded images) is automatically migrated into the new table, with markdown content converted to HTML. Any external client applications which read or write the notes field directly via the API will need to be updated to use the new endpoint.

Formal State Transitions

PR #12507 switches build and order status transitions to a more formal finite-state-machine approach. As part of this change, attempting an invalid or repeated state transition now raises a ValidationError instead of silently failing. Plugins which implement custom transitions should review this change and adjust their usage accordingly to take advantage of the new safeguards.

Tags Filter Renamed

PR #12672 renames the tags filter — added in 1.4.0 for filtering models by tag — to tag_name, to avoid a name clash with the tags field exposed on the same endpoints. Any integration filtering tagged objects via ?tags= must be updated to use ?tag_name= instead.

Squash Migrations Prior to 1.0.0

PR #12830 squashes all database migrations predating the 1.0.0 release. Any installation still running a pre-1.0.0 version of InvenTree must first update to 1.0.0 before updating to this release.

API Token Storage Hardened

PR #12850 changes how API tokens are stored, replacing plaintext storage with a peppered HMAC-SHA256 digest, so that gaining read access to the database (for example via a side-channel or IDOR vulnerability) can no longer be used to recover usable API tokens. Newly-issued tokens use a longer “v2” format; existing tokens continue to work, but since the raw token value can no longer be read back from the database, calling /api/user/me/token/ now always reissues (and invalidates) the token rather than returning the existing value.

Security Fixes

A number of security vulnerabilities have been fixed in this release.

Attachment API Permission Bypass

PR #12689 fixes a flaw in the Attachment API where user role permissions were not checked against the owning model, allowing any authenticated user to enumerate and download attachments they should not have had access to. The API now checks the requesting user’s view permissions and returns PermissionDenied where appropriate.

Metadata Endpoint Information Disclosure

PR #12771 restricts the generic metadata API endpoints to a fixed set of safe lookup fields, closing a path where arbitrary field names could be used to perform unintended database queries and recover data outside the intended scope.

Data Import Session Retargeting

PR #12809 prevents the target model type of a data import session from being changed after the import has started, closing a gap where a user could bypass the authorization check performed against the original target model.

Stock Locate Permission Check

PR #13000 adds a missing permission check to the “locate stock” plugin action endpoint, which previously allowed any authenticated user to trigger the action and enumerate stock regardless of their assigned role.

Additional Hardening

A number of smaller permission and hardening fixes are also included in this release:

  • Calendar .ics feeds (PR #12764) and the SelectionList API (PR #12763) now correctly check user permissions
  • Users may only edit their own profile, and may only access notes or parameters against models they are scoped to (PR #12766)
  • The /api/user/me/ endpoint can no longer be used to delete your own account (PR #12770)
  • The MachineSettingList endpoint now requires the admin role, and barcode generation is permission-checked (PR #12886)
  • Potentially dangerous tags are stripped from uploaded SVG files (PR #12687)
  • User-facing input is sanitized more robustly before being rendered into WeasyPrint reports (PR #12997)
  • New secret keys are now generated using Django’s own helper rather than a custom implementation (PR #12999)
  • Installer scripts have been hardened against a number of possible injection points (PR #12819)
  • InvenTree now warns administrators if an unsafe wildcard CORS configuration is detected (PR #12773)

Security Advisories

The following security advisories have been published in relation to this release:

  • https://github.com/inventree/InvenTree/security/advisories/GHSA-9mm7-c3mq-6c99
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-hv74-9q5w-p8v3
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-p9q2-5w65-82g5
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-q6vh-g752-53g8

For more information, please refer to our security advisories page

Database Changes

This release includes a number of changes to the underlying database schema and data validation. As always, a backup of your database is recommended before performing the update.

Legacy Session Table Cleanup

PR #12675 removes a legacy database table left behind on older installations that predate the removal of the django-user-sessions package, fixing a foreign-key error that could occur when deleting a user. PR #12697 is a follow-up fix ensuring this migration also runs correctly on MySQL-backed installations.

Notes Migration Fix for MySQL

PR #12808 fixes the data migration introduced by the notes refactor (PR #11971), which did not run correctly on MySQL due to differences in how that backend returns rows created via bulk_create. Migration regression testing is now performed against all supported database backends to catch this class of issue earlier.

Shipment & Address Contact Fields

PR #13016 adds a contact field to the SalesOrderShipment model, and phone_number and email fields to the Address model, allowing more complete contact details to be recorded against shipments and addresses.

New Features

Internal Companies & Purchase Order Delivery Address

PR #13017 introduces the concept of an “internal” company — a flag on the Company model used to represent your own organization, configurable via the new INVENTREE_DEFAULT_INTERNAL_COMPANY setting and exposed to report templates as internal_company. Building on this, PR #9768 adds a dedicated delivery address field to purchase orders, which must reference an internal company.

Docker Compose Health Checks

PR #12124 adds health checks to each container in the Docker Compose stack, with dependent containers now waiting for their dependencies to report healthy before starting (for example, the worker waits on the server, and the server waits on the database and cache).

Cut-to-Length BOM Items

PR #12422 adds piece_count and piece_size fields to BOM items, for assemblies that require a number of discrete pieces cut from continuous stock such as cable, tubing, or structural profiles. When a piece size is specified, the total required quantity is calculated automatically, while still preserving the per-piece information needed for purchasing and production.

Persistent Previous/Next Navigation

PR #12585 improves detail-page navigation from filtered tables: Previous and Next controls now remember the filtered result set via the URL, and a subtle “x of y” indicator shows your position within it, making it much easier to step through a filtered list of parts, orders, or other items.

Bulk-Edit Return Order Line Items

PR #12635 allows the outcome of multiple return order line items to be changed at once, rather than editing each line individually.

Expanded Identity Federation: SCIM, OIDC & SAML

This release brings together a larger identity federation initiative. PR #12713 adds SCIM 2.0 support for provisioning users and groups from an external identity provider. PR #12731 switches the built-in OIDC/OAuth2 provider on by default (previously available but opt-in), and consolidates the related settings into the Admin Center. PR #12799 rounds this out with a guided SAML configuration helper in the frontend, making it easier to connect InvenTree to a SAML-based identity provider.

Plugin Well-Known URLs

PR #12698 adds a mixin allowing plugins to register entries under the .well-known path, useful for authentication discovery and other system integrations.

Faster Bulk Data Import

PR #12792 adds an opt-in bulk-create mode to the import-records management task, dramatically speeding up large dataset imports (in testing, a 1.2 million row dataset dropped from around 16 minutes to roughly 1 minute).

Stock Location Owner Field in the UI

PR #12826 exposes the Owner field on the stock location create/edit form, restoring parity with the stock item form and matching documented (but previously missing) UI behavior.

Rotated Table Headers

PR #12837 adds a user setting which renders long table column titles vertically rather than horizontally, saving significant horizontal space in parameter-heavy tables. The option is off by default.

Hide Unused Order Types from the UI

PR #12842 adds administrator toggles to fully hide Sales Order, Purchase Order, or Build Order functionality from the interface, for instances that don’t make use of them.

Plugin Custom Pages

PR #12900 adds a new route UI feature type, allowing plugins to register entirely new frontend pages (served under /web/plugin/<plugin>/...) in addition to the existing panel and dashboard widget integration points.

Default Receive Location

PR #12911 adds a global setting to configure a default stock location for receiving items against purchase orders.

Global Batch Code for Purchase Order Receipt

PR #12912 adds a batch code that can be set once when receiving a purchase order and applied across all received items, with the option to override it on individual line items.

Background Task Timeouts & Single-Shot Mode

PR #12913 adds per-task timeout configuration and an optional single-shot mode (disabling automatic retry on failure) for background tasks, giving more control over long-running or non-idempotent jobs.

Per-User Notification Localization

PR #12944 renders notification emails and in-app messages in each recipient’s own language preference, rather than the server process’s default locale, with efficient per-locale batching for email delivery.

Nested BOM Display

PR #12952 implements a true nested BOM view, replacing the previous reduced-dataset subassembly table and displaying the total quantity of each sub-item — including across multiplier chains of nested subassemblies.

Pinned, Resizable Navigation Sidebar

PR #12974 adds an optional side-by-side navigation tree that stays pinned alongside the main content. It can be resized via a splitter (collapsing automatically when dragged small), and toggled on from user settings or a pin button in the header.

First-Time User Guide

PR #12978 adds a short, dismissible onboarding tour for new users, along with backend data structures to support further guided tours in future releases.

Plugin Reload Cycle Detection

PR #13007 improves automatic plugin reload handling and documents its limitations — binary plugins and changed dependencies cannot be hot-reloaded. The system now detects and reports plugin reload cycles instead of looping indefinitely.

Bug Fixes

As always, we have provided a number of bug fixes with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!

Contributing

InvenTree is an open source project, and we welcome contributions from the community. There are many ways to contribute to the project, including code contributions, translation efforts, documentation improvements, and financial support.

New Contributors

As always we would like to thank all of our contributors for their hard work and dedication to the InvenTree project. In particular, we would like to welcome the following new contributors who have made their first contributions in this release:

  • @FurinaDog made their first contribution in https://github.com/inventree/InvenTree/pull/12616
  • @ribsey made their first contribution in https://github.com/inventree/InvenTree/pull/12550
  • @amanjain57-gif made their first contribution in https://github.com/inventree/InvenTree/pull/12422
  • @Alonso-Lopez-1 made their first contribution in https://github.com/inventree/InvenTree/pull/12286
  • @Jr-kenny made their first contribution in https://github.com/inventree/InvenTree/pull/12585
  • @psxjt5 made their first contribution in https://github.com/inventree/InvenTree/pull/12703
  • @wyyd-yxc made their first contribution in https://github.com/inventree/InvenTree/pull/12826
  • @lizerui1608-dev made their first contribution in https://github.com/inventree/InvenTree/pull/12888
  • @fquinto made their first contribution in https://github.com/inventree/InvenTree/pull/12926
  • @BI7KHI made their first contribution in https://github.com/inventree/InvenTree/pull/12784
  • @xyz-is-best made their first contribution in https://github.com/inventree/InvenTree/pull/12944
  • @maxgr0 made their first contribution in https://github.com/inventree/InvenTree/pull/12973
  • @gotoUSA made their first contribution in https://github.com/inventree/InvenTree/pull/12990
  • @tijsmoree made their first contribution in https://github.com/inventree/InvenTree/pull/12966

Code Contributions

Check out our GitHub page for a list of outstanding issues and feature requests. If you are a developer or want to become one, you can help to contribute to the project by submitting a pull request.

Translation

Our translation efforts continue to grow, with coverage increasing across a wide range of languages. We are grateful to all of our translators who have contributed to making InvenTree accessible to users around the world.

If you are interested in contributing to the translation efforts, please visit our Crowdin project and join the community of translators.

Documentation / Technical Writing

If you have experience with technical writing, you can help to improve the InvenTree documentation. We are always looking for help to improve the documentation and make it more accessible to new users.

Report Bugs

If you encounter a bug in InvenTree, please report it on our GitHub issues page. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.

Financial Contributions

Sponsorships help to keep this project sustainable, and buys time for the core developers to commit to the project. A recurring or one off sponsorship is a great way to help InvenTree development to continue at full steam!

The work undertaken to keep InvenTree running is done by a very small group of core developers, who do so in their spare time (and are not sponsored by their employers to work on InvenTree). If you benefit from the InvenTree project, please consider contributing to maintain vibrant development of this software!

If you are using InvenTree in a commercial setting, please consider sponsoring the project to help support ongoing development and maintenance. Your support is greatly appreciated and helps to ensure that InvenTree remains a viable and sustainable project for years to come.

If your company benefits from InvenTree, please consider a one time sponsorship or a recurring sponsorship to help support the project.

]]>
SchrodingersGat
InvenTree MCP Plugin2026-09-17T00:00:00+00:002026-09-17T00:00:00+00:00/blog/2026/09/17/inventree-mcpThe InvenTree development team is excited to introduce InvenTreeMCP, a new plugin which exposes your InvenTree inventory data to AI agents and other MCP-aware applications via the Model Context Protocol (MCP).

What is it for?

MCP is an open standard which allows AI assistants - such as Claude - to interact with external tools and data sources in a structured way. InvenTreeMCP implements an MCP server as an InvenTree plugin, allowing any MCP client to query your InvenTree instance directly, over a Streamable HTTP endpoint.

This means you can ask an AI assistant questions about your inventory - stock levels, open orders, BOM structures, and more - and have it query your live InvenTree data to provide an answer, without needing to write any custom integration code.

Under the hood, InvenTreeMCP is implemented as a thin layer on top of the existing InvenTree API. Every request made by an MCP client passes through the same permission checks and filtering as a normal API call, so users only ever see the data they are already allowed to access.

What tools does it expose?

InvenTreeMCP currently exposes read access to the core InvenTree data model, including:

  • Parts and part categories
  • Stock items and stock locations
  • Purchase, sales, return and build orders (and their line items)
  • Companies and contacts
  • Manufacturer and supplier parts
  • Bill of materials (BOM) items
  • Attachments and parameters
  • Stock tracking history and test results
  • Project codes

Tool schemas and available filters are generated automatically from InvenTree’s existing API serializers, so the tools exposed to MCP clients stay in sync with the underlying data model as InvenTree evolves.

How can it be used?

InvenTreeMCP can be installed like any other InvenTree plugin:

  1. Install the plugin, e.g. via pip: pip install inventree-mcp
  2. Enable the plugin under Admin > Plugins
  3. Generate an API token in InvenTree for your MCP client to use

Once installed and enabled, the MCP server is available at a URL such as https://<your-inventree-server>/plugin/inventree-mcp/mcp/. Most MCP clients which support remote (Streamable HTTP) servers can be pointed directly at this endpoint, authenticating with an InvenTree API token, e.g.:

{
  "mcpServers": {
    "inventree": {
      "url": "https://<your-inventree-server>/plugin/inventree-mcp/mcp/",
      "headers": {
        "Authorization": "Token <your-api-token>"
      }
    }
  }
}

For clients which only support local (stdio) MCP servers, the mcp-remote bridge can be used to connect to the same endpoint.

In addition to API tokens, the plugin also supports authentication via username/password, or OAuth2 bearer tokens with optional scope restrictions - useful if you want to issue narrowly-scoped credentials to a particular agent.

By default, the plugin runs in read only mode, which blocks any write operations regardless of the permissions of the authenticating user. This is a sensible default while you get a feel for how your AI tooling of choice interacts with your InvenTree data.

Feedback Welcome

InvenTreeMCP is a brand new plugin, and this is very much a first step towards richer AI integration with InvenTree. We would love to hear how you’re using it, and what’s working (or not working) for your setup.

If you run into any bugs, or have trouble with installation or configuration, please open an issue on the GitHub repository.

If there are additional tools or data types you’d like to see exposed via MCP, we’d also love to hear your suggestions - feel free to raise a feature request on the same issue tracker.

]]>
SchrodingersGat
Action required - Package Repository Change2026-09-09T00:00:00+00:002026-09-09T00:00:00+00:00/blog/2026/09/09/package-repoDue to changes to the package publishing platform, packager.io, all users of the package-based installer (most often installed through the 1-line install script) must manually update their package repository configuration to continue receiving updates.

The following Bash commands will ensure that you continue receiving updates from the new package repository configuration. The update procedure, package structure and general commands are unchanged.

Upgrade Instructions

Command for Ubuntu 26.04

sudo curl -fsSL "https://go.packager.io/srv/deb/inventree/InvenTree/gpg-key.gpg" -o /usr/share/keyrings/InvenTree.gpg
sudo curl -fsSL "https://go.packager.io/srv/inventree/InvenTree/stable/installer/ubuntu/26.04.list" -o /etc/apt/sources.list.d/InvenTree.list
sudo apt update
sudo apt install -y inventree

Command for Ubuntu 24.04

sudo curl -fsSL "https://go.packager.io/srv/deb/inventree/InvenTree/gpg-key.gpg" -o /usr/share/keyrings/InvenTree.gpg
sudo curl -fsSL "https://go.packager.io/srv/inventree/InvenTree/stable/installer/ubuntu/24.04.list" -o /etc/apt/sources.list.d/InvenTree.list
sudo apt update
sudo apt install -y inventree

Command for Debian 13

sudo curl -fsSL "https://go.packager.io/srv/deb/inventree/InvenTree/gpg-key.gpg" -o /usr/share/keyrings/InvenTree.gpg
sudo curl -fsSL "https://go.packager.io/srv/inventree/InvenTree/beta/installer/debian/13.list" -o /etc/apt/sources.list.d/InvenTree.list
sudo apt update
sudo apt install -y inventree

Supported OS versions - you might need to upgrade

We are phasing out versions of Ubuntu and Debian that are at, or approaching, end of support, particularly as Python 3.11 has only one year until EOL.

If you are on Ubuntu 20.04 (LTS) - which many of the old Docker droplet deployments were on - it is strongly recommended to update to 26.04 (LTS) to continue receiving updates. This will likely also require you to update your postgres version to at least 14, recommended is 17 or 18. Note that postgres updates should be done in single version steps (13 -> 14 -> 15 -> 16 -> 17 -> 18) or with pgupgrade.
The volunteer InvenTree core team does not have the resources to assist with individual upgrades.

Additional Notes on OS version selections

As of InvenTree version 1.5.3, the supported versions are Debian 13 and Ubuntu 24.04 / 26.04 LTS. This is mainly because Bookworm is the only supported Debian release shipping Python 3.11 (as does Ubuntu 22.04).

As Python 3.11 has received only security updates since 2024 and will reach EOL in October 2027, the libraries on which we depend have increasingly announced that they will soon end support for it. Although most still support it, this is likely to change. Therefore, we are raising the minimum versions in advance so that we are not caught off guard by dependency issues that require urgent releases.

Python 3.12 also has some nice QoL features that developers using Python 3.14 (myself included) can forget are relatively new. It also drops distutils and a few importlib functions. Raising the minimum versions allows us to drop shims and use these newer features.

Acknowledgements

We are very thankful to Cyril Rohr for packager.io and the support provided on various issues and questions throughout the years. We are not switching away from his solutions, but using the newer version, go.packager.io, as the old one is being sunset in the near future.

]]>
matmair
1.5.0 Release2026-08-09T00:00:00+00:002026-08-09T00:00:00+00:00/blog/2026/08/09/1.5.0InvenTree 1.5.0 has been released! This release includes a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.

Changelog

Major changes are documented in the CHANGELOG.md file in the repository. For a full list of changes, please refer to the release notes.

Update Procedure

To update to the latest version of InvenTree, please follow the updating instructions provided in the InvenTree documentation. Note that the particular update procedure may vary depending on your installation method.

Breaking Changes

While we strive to maintain backward compatibility, there are some breaking changes in this release. While many of these are minor, and should not affect most users, we recommend that you review the list of breaking changes to ensure that your installation will continue to function as expected after the update. Each breaking change is documented in detail at the links below:

API Throttling Enabled by Default

PR #11951 enables API request throttling by default, providing a first line of defense against trivial denial-of-service abuse of API endpoints. The default limits are intentionally generous so as to minimize impact on most instances, but administrators of smaller or resource-constrained instances should review the new throttling configuration.

Bump Minimum Python Version

PR #12223 raises the minimum supported Python version to 3.12, and drops pre-built packages for Debian 11 and Ubuntu 22.04. Users running InvenTree on an older Python version, or on one of these older distributions, will need to upgrade their environment before installing this release.

Table Field Refactor

PR #12274 rewrites how “table” fields are rendered in UI forms, fixing a number of performance issues where rows were needlessly re-created on every update. As part of this refactor, each row now requires a unique ID value. Any custom plugins that use “table” field types in UI forms will need to be adjusted to match the new configuration.

Refactor API for Duplicating Objects

PR #12294 consolidates the various object-duplication endpoints behind a single DuplicateOptionsSerializer, and extends duplication support to additional models (including the ability to copy notes). Integrations which rely on the previous per-model duplication endpoints should be reviewed against the new consolidated API.

Adjust Default Behavior of “migrate” Command

PR #12320 changes the default behavior of the invoke update command so that it no longer automatically generates new migration files when the database schema has changed. This prevents installations from ending up with out-of-line migration files that were not committed to the repository. Developers who rely on migrations being auto-generated during update will need to generate them explicitly.

Remove Dead Pricing Code on Part Model

PR #12357 removes a number of legacy pricing methods from the Part model, in preparation for a larger pricing refactor. While this does not affect any internally called code, any plugins relying on these legacy methods being available will need to be adjusted.

Remove MPTT Mixin from StockItem Model

PR #12360 removes the MPTT tree mixin from the StockItem model. The model never made real use of MPTT’s tree features, but paid the cost of expensive tree rebuilds and fragile concurrency locking on every bulk stock operation. Removing it reduces database load and eliminates a class of concurrency issues during bulk stock actions. External clients should note that the tree-related fields previously exposed on StockItem are no longer available via the API.

Optional Field Permissions

PR #12529 fixes a permission gap where “optional fields” exposing cross-model relations were returned regardless of whether the requesting user had permission to view the related model. These optional fields are now excluded from API responses if the user lacks view permission on the associated model, so integrations that depended on always receiving these fields may need to handle their absence.

Security Fixes

A number of security vulnerabilities have been fixed in this release.

Fix Permissions for Group and RuleSet Endpoints

PR #12563 tightens access to the group and RuleSet API endpoints, which previously only checked the is_staff flag. These endpoints now also require the user to hold the StaffRole permission, closing a gap that allowed staff users without the appropriate role to view or modify permission rulesets.

Additional SSRF Protections

PR #12595 further tightens the protections around fetching data from external URLs, reducing the risk of server-side request forgery (SSRF) when InvenTree makes outgoing requests on a user’s behalf.

Database Changes

This release includes a number of changes to the underlying database schema and data validation. As always, a backup of your database is recommended before performing the update.

Fix for UUID Fields

PR #12301 introduces a custom UUID field to work around a Django 5.0 change to UUIDField handling on MariaDB. This resolves migration issues that could occur when updating existing UUID columns on MariaDB-backed installations.

Fix Currency Choices for PartPricing Model

PR #12336 removes the dynamically-generated currency choices from the PartPricing model definition, moving that validation into the API serializer instead, along with a dedicated validator to ensure only supported currency codes can be assigned.

Unique Parameters

PR #12388 adds uniqueness validation options to the ParameterTemplate model, allowing administrators to enforce that values for a given parameter template must be unique across parts.

Data Import Fix

PR #12568 fixes an encoding issue that could occur when importing date values from Excel files during the data import process.

New Features

Tree Select in Form Fields

PR #12217 adds a hierarchical “tree select” control for choosing stock locations and part categories in UI forms, making it much easier to navigate deeply nested location and category structures when filling out a form.

Snippet Editor

PR #12299 adds a dedicated UI for managing report assets and snippets, making it easier to create and maintain reusable template fragments for report and label generation.

Form Submission Shortcut

PR #12328 adds a keyboard shortcut (Ctrl + Enter) to submit the currently open form, speeding up repetitive data-entry workflows.

Break Apart Assemblies

PR #12310 introduces a long-requested “disassembly” feature, allowing an assembly to be broken apart back into its constituent BOM items. The feature is supported for untracked, tracked (serialized), and mixed assemblies, and preserves the originating purchase order and build order history on the resulting stock items.

Preview Drawer

PR #12117 adds a global “preview drawer” which provides a quick-view of a part, stock item, order, or other object without navigating away from the current page. Preview rendering is available for all core models, and is also exposed to plugins so they can supply their own preview content.

Bug Fixes

As always, we have provided a number of bug fixes with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!

Contributing

InvenTree is an open source project, and we welcome contributions from the community. There are many ways to contribute to the project, including code contributions, translation efforts, documentation improvements, and financial support.

New Contributors

As always we would like to thank all of our contributors for their hard work and dedication to the InvenTree project. In particular, we would like to welcome the following new contributors who have made their first contributions in this release:

  • @suzunn made their first contribution in https://github.com/inventree/InvenTree/pull/12215
  • @ledvinap made their first contribution in https://github.com/inventree/InvenTree/pull/12332
  • @br413 made their first contribution in https://github.com/inventree/InvenTree/pull/12413
  • @Leopoldius made their first contribution in https://github.com/inventree/InvenTree/pull/12424
  • @aamirasmal15 made their first contribution in https://github.com/inventree/InvenTree/pull/12423
  • @impuls42 made their first contribution in https://github.com/inventree/InvenTree/pull/12432
  • @snipe made their first contribution in https://github.com/inventree/InvenTree/pull/12452
  • @bhumin18 made their first contribution in https://github.com/inventree/InvenTree/pull/12440
  • @hanielee made their first contribution in https://github.com/inventree/InvenTree/pull/12392
  • @jayasree-007 made their first contribution in https://github.com/inventree/InvenTree/pull/12533

Code Contributions

Check out our GitHub page for a list of outstanding issues and feature requests. If you are a developer or want to become one, you can help to contribute to the project by submitting a pull request.

Translation

Our translation efforts continue to grow, with coverage increasing across a wide range of languages. We are grateful to all of our translators who have contributed to making InvenTree accessible to users around the world.

If you are interested in contributing to the translation efforts, please visit our Crowdin project and join the community of translators.

Documentation / Technical Writing

If you have experience with technical writing, you can help to improve the InvenTree documentation. We are always looking for help to improve the documentation and make it more accessible to new users.

Report Bugs

If you encounter a bug in InvenTree, please report it on our GitHub issues page. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.

Financial Contributions

Sponsorships help to keep this project sustainable, and buys time for the core developers to commit to the project. A recurring or one off sponsorship is a great way to help InvenTree development to continue at full steam!

The work undertaken to keep InvenTree running is done by a very small group of core developers, who do so in their spare time (and are not sponsored by their employers to work on InvenTree). If you benefit from the InvenTree project, please consider contributing to maintain vibrant development of this software!

If you are using InvenTree in a commercial setting, please consider sponsoring the project to help support ongoing development and maintenance. Your support is greatly appreciated and helps to ensure that InvenTree remains a viable and sustainable project for years to come.

If your company benefits from InvenTree, please consider a one time sponsorship or a recurring sponsorship to help support the project.

]]>
SchrodingersGat
1.4.0 Release2026-06-16T00:00:00+00:002026-06-16T00:00:00+00:00/blog/2026/06/16/1.4.0InvenTree 1.4.0 has been released! This release includes a number of new features, improvements, and bug fixes. We recommend all users to update to this version as soon as possible.

Changelog

Major changes are documented in the CHANGELOG.md file in the repository. For a full list of changes, please refer to the release notes.

Update Procedure

To update to the latest version of InvenTree, please follow the updating instructions provided in the InvenTree documentation. Note that the particular update procedure may vary depending on your installation method.

Breaking Changes

While we strive to maintain backward compatibility, there are some breaking changes in this release. While many of these are minor, and should not affect most users, we recommend that you review the list of breaking changes to ensure that your installation will continue to function as expected after the update. Each breaking change is documented in detail at the links below:

Adjust API Endpoint Status Code Return Values

PR #11723 removes various API quirks and aligns the InvenTree API with REST conventions: some operations have been moved to the correct HTTP methods (e.g. GET → POST), HTTP status codes now follow standard conventions rather than custom values, and custom permissions on the notifications endpoint have been removed. Users with custom API integrations should review their code for reliance on the previous non-standard behavior.

Enforce Order “issued_by” Field as Read-Only

PR #11816 makes the issued_by field on BuildOrder (and related order models) read-only in the API; it is now automatically populated with the user who created the order and can no longer be manually overridden. Any integrations or scripts that previously wrote to this field will need to be updated.

Node.js Build Environment Upgraded to v24

PR #11893 upgrades the frontend build environment from Node.js 20 (which reached end-of-life on April 30, 2025) to Node.js 24. Developers building InvenTree from source must upgrade their local Node.js installation to v24 or later.

Report and Label Plugin Context Changes

PR #11941 fixes a long-standing bug where user information was unavailable in report and label generation contexts. As part of this fix, the signatures for custom report plugin methods (add_report_context(), add_label_context(), and report_callback()) have changed: they now receive an explicit user object instead of a request object (which was previously always None in background workers). Plugin developers must update their implementations accordingly.

Remove Remote Image Download Support

PR #11962 removes the remote_image field from the Part API endpoint, eliminating the ability to supply a remote URL to download a part image from an external source. This feature was removed due to security concerns around server-side outgoing requests; image uploads via other mechanisms (such as clipboard paste) remain supported.

Fix Resistor RKM Notation Parsing

PR #12065 corrects how RKM-style resistor values (e.g. 10R, 4R7) are parsed by ensuring the R delimiter is interpreted as ohms rather than being misread by the unit parser. Parts or parameters that previously relied on the incorrect parsing behavior may need to be reviewed.

Fix Meaning of SHIPPED Status in SalesOrderStatusGroups

PR #12107 corrects a misclassification of the SHIPPED sales order status: it has been moved from the COMPLETE group to the ACTIVE group in SalesOrderStatusGroups. Any external code or integrations that filter orders based on these status groups will need to be updated to reflect this corrected grouping.

Report Printing Permission Enforcement

PR #12142 tightens permissions for report and label printing: users must now have VIEW permission on the target model in order to print a report against it, and printing against disabled templates is blocked. Users or integrations that previously relied on printing without explicit view permissions may find certain print actions now return a permission error.

Security Fixes

A number of security vulnerabilities have been fixed in this release.

Django Security Update

PR #11907 bumps Django to the latest security release, addressing vulnerability GHSA-5h8x-9c6f-2j8m. All users are encouraged to update promptly to benefit from this patch.

Admin Interface Permission Restrictions

PR #12036 tightens Django admin permissions to align with the API’s own access controls. Scheduled tasks are now read-only in the admin panel and certain actions are restricted to superusers only, reducing the risk of unauthorized modification of critical system configuration through the admin interface.

Report Printing Permission Enforcement

PR #12142 enforces that users must hold VIEW permission on the target model in order to print a report or label against it, and prevents printing against disabled templates. This closes a path by which users could access model data indirectly through the report printing API without the appropriate permissions.

Switch Node.js Version Manager from n to nvm

PR #12140 replaces the n Node.js version manager with nvm (Node Version Manager) in the Docker build and CI environment. Using the officially maintained nvm toolchain reduces supply-chain risk compared to the third-party n package.

PDF Report Generation Security Hardening

PR #12160 hardens the WeasyPrint-based PDF report generator against two classes of attack. The file:// URI scheme is now fully disabled in report templates, preventing arbitrary server-side file reads, and SSRF protections have been added for remote URL lookups — with remote URL fetching disabled by default. Users whose report templates reference remote URLs will need to explicitly enable that capability via the new configuration setting.

API Permissions Fix

PR #12168 improves API security by reducing the scope of permissions required for certain API endpoints.

Security Advisories

The following security advisories have been published in relation to this release:

  • https://github.com/inventree/InvenTree/security/advisories/GHSA-45f6-v6jq-99f7
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-7w96-99fj-8g7x
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-568x-qh23-wh8g
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-xjpv-cwpw-7qx8
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-c9wp-mw98-gfrj
  • https://github.com/inventree/InvenTree/security/advisories/GHSA-6pm3-m334-mr4j

For more information, please refer to our security advisories page

New Features

Transfer Orders

PR #11281 introduces a new Transfer Order type for formalizing and tracking internal stock movements between locations. Users can create transfer orders with specific source and destination locations, allocate stock to line items, and complete the transfer to move inventory — providing a full audit trail for inter-location stock movements.

BOM Permission Ruleset

PR #11825 adds a dedicated permission ruleset for Bill of Materials management, allowing administrators to control which user groups can view, edit, or modify BOMs independently of other part permissions. Existing user permissions are preserved via a data migration.

BOM Row Expand

PR #11809 enables multi-level BOM expansion in the UI, letting users expand individual BOM rows to inspect nested subassemblies inline without switching away from the BOM view. A user-level setting controls whether subassembly expansion is shown by default.

BOM Compare

PR #11853 adds a BOM comparison tool accessible from the part detail view, allowing side-by-side comparison of two assemblies’ Bills of Materials. Comparisons can also be linked to directly via URL parameters.

Maximum Stock Level

PR #11914 adds a maximum stock level field to parts, complementing the existing minimum stock tracking to provide full min/max inventory management. A new “high stock” filter in the part table makes it easy to identify items that have exceeded their upper limit.

Attachment Image Thumbnails

PR #11961 improves attachment handling by detecting image attachments and displaying thumbnail previews in the attachment table. This release also adds a configurable maximum file upload size for administrators.

Sales Order Auto-Allocate

PR #12000 brings automatic stock allocation to sales orders, matching the existing behavior on build orders. Users can auto-allocate available stock to order line items with configurable sorting preferences (e.g. by expiry date or serial number), and can bulk-delete allocations through the UI and API.

Stock Item Creation Date

PR #12011 adds a creation_date field to the StockItem model, capturing when each stock item first entered the system. The field is exposed in the API (with filtering and ordering support) and displayed in the stock item table.

Hot Module Replacement for Plugins

PR #12060 enables Hot Module Replacement (HMR) and React Fast Refresh in the Vite development server for InvenTree plugins. Plugin developers can now see code changes reflected instantly without a full page reload, significantly speeding up the plugin development workflow.

Tags Support

PR #12077 introduces a comprehensive tagging system across InvenTree, covering parts, orders, companies, stock items, and more. Tags can be managed via the API and used to filter tables, providing a flexible way to categorize and locate items without changing the data model.

Saved Table Filter Sets

PR #12079 allows users to save named sets of table filters and reload them with a single click. This is particularly useful for frequently repeated filter configurations across tables and calendar views.

Calendar Month Scrolling

PR #12092 enables multi-month scrolling in calendar views, making it much easier to plan and schedule across extended time horizons. A configurable “calendar horizon” parameter allows the view to be set back to a single month if preferred.

Table Column Filters

PR #12103 exposes filter controls directly in table column headers, so users can add, edit, or remove filters without opening a separate filter panel. Active filters are also indicated visually on the relevant column headers.

Remember Last Used Print Template and Printer

PR #12146 persists the user’s last selected label template and printer plugin per model type, so the printing dialog reopens with the same settings as the previous session. This eliminates the need to reselect template and printer on every print action.

Hotkey Helper Modal

PR #12128 adds a hotkey registration system and a discoverable helper modal that lists all currently active keyboard shortcuts — including those registered by plugins and mounted components. The modal is accessible via the spotlight interface, making it easy for users to find and learn available shortcuts.

Calendar Event Tooltips

PR #11980 adds detailed tooltips to calendar event entries across purchase order and build calendar views. Hovering over an event now shows contextual information without requiring the user to navigate away from the calendar.

Line Number Natural Sort

PR #11885 fixes the sorting of line numbers on orders so they sort numerically (1, 2, 3, 10) rather than alphabetically (1, 10, 2, 3). This improves the readability of order line items and ensures a more intuitive ordering.

Bug Fixes

As always, we have provided a number of bug fixes with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!

Contributing

InvenTree is an open source project, and we welcome contributions from the community. There are many ways to contribute to the project, including code contributions, translation efforts, documentation improvements, and financial support.

New Contributors

As always we would like to thank all of our contributors for their hard work and dedication to the InvenTree project. In particular, we would like to welcome the following new contributors who have made their first contributions in this release:

  • @hartigdan made their first contribution in https://github.com/inventree/InvenTree/pull/11735
  • @ZhangzrJerry made their first contribution in https://github.com/inventree/InvenTree/pull/11746
  • @DanielDango made their first contribution in https://github.com/inventree/InvenTree/pull/11868
  • @robertsilen made their first contribution in https://github.com/inventree/InvenTree/pull/11950
  • @Idea-Junkie made their first contribution in https://github.com/inventree/InvenTree/pull/11369
  • @xhivo97 made their first contribution in https://github.com/inventree/InvenTree/pull/12060
  • @getpwnam made their first contribution in https://github.com/inventree/InvenTree/pull/12078
  • @NerosKi made their first contribution in https://github.com/inventree/InvenTree/pull/12094
  • @Nasawa made their first contribution in https://github.com/inventree/InvenTree/pull/12151
  • @Sanidhyavijay24 made their first contribution in https://github.com/inventree/InvenTree/pull/12146
  • @kaizeenn made their first contribution in https://github.com/inventree/InvenTree/pull/12162
  • @johnluetke made their first contribution in https://github.com/inventree/InvenTree/pull/11982
  • @geekcj12 made their first contribution in https://github.com/inventree/InvenTree/pull/12203
  • @aslushnikov made their first contribution in https://github.com/inventree/InvenTree/pull/12219
  • @reid-p made their first contribution in https://github.com/inventree/InvenTree/pull/12227

Code Contributions

Check out our GitHub page for a list of outstanding issues and feature requests. If you are a developer or want to become one, you can help to contribute to the project by submitting a pull request.

Translation

Our translation efforts continue to grow, with coverage increasing across a wide range of languages. We are grateful to all of our translators who have contributed to making InvenTree accessible to users around the world.

If you are interested in contributing to the translation efforts, please visit our Crowdin project and join the community of translators.

Documentation / Technical Writing

If you have experience with technical writing, you can help to improve the InvenTree documentation. We are always looking for help to improve the documentation and make it more accessible to new users.

Report Bugs

If you encounter a bug in InvenTree, please report it on our GitHub issues page. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.

Financial Contributions

Sponsorships help to keep this project sustainable, and buys time for the core developers to commit to the project. A recurring or one off sponsorship is a great way to help InvenTree development to continue at full steam!

The work undertaken to keep InvenTree running is done by a very small group of core developers, who do so in their spare time (and are not sponsored by their employers to work on InvenTree). If you benefit from the InvenTree project, please consider contributing to maintain vibrant development of this software!

If you are using InvenTree in a commercial setting, please consider sponsoring the project to help support ongoing development and maintenance. Your support is greatly appreciated and helps to ensure that InvenTree remains a viable and sustainable project for years to come.

If your company benefits from InvenTree, please consider a one time sponsorship or a recurring sponsorship to help support the project.

]]>
SchrodingersGat
1.3.0 Release2026-04-11T00:00:00+00:002026-04-11T00:00:00+00:00/blog/2026/04/11/1.3.0The InvenTree team is excited to announce the release of version 1.3.0. This release includes numerous new features, improvements, and bug fixes.

Changelog

Major changes are documented in the CHANGELOG.md file in the InvenTree repository.

For a full list of changes made in this release, please refer to the release notes.

Update Procedure

To update to the latest version of InvenTree, please follow the updating instructions provided in the InvenTree documentation. Note that the particular update procedure may vary depending on your installation method.

Breaking Changes

The following changes may require updates to custom plugins, API clients, or other integrations with the InvenTree application. Please review these changes carefully before updating to version 1.3.0.

Supplier Part Model Changes

In #11303 we have made a change to the implementation of the supplier part model. While this will not impact most InvenTree users, it may change how custom plugins or external API clients interact with the InvenTree application.

Previously, the Part model had a default_supplier field, which pointed to a single instance of the SupplierPart model. This field has been removed, and instead the SupplierPart model has a primary field - which is a boolean field indicating whether this supplier part is the primary supplier for the associated part. This change allows for more flexible supplier management.

Plugin Data Import

In #11648 we have added the ability to import custom plugin data from an external data file during the import process. This allows custom plugin data to be migrated across InvenTree instances if required.

Sqlite Support

In #11500 we have made some changes to our support for Sqlite databases. The default implementation now uses a significantly longer connection timeout, and uses write-ahead logging (WAL) mode by default. This should help to reduce the likelihood of database lockouts when using Sqlite, particularly in environments where multiple users may be accessing the database concurrently.

Security Fixes

There have been a number of security fixes included in this release. We would like to thank the security researchers who have responsibly disclosed these issues to us, and we encourage anyone who discovers a potential security vulnerability in InvenTree to report it to us via our security policy.

Advisories

The following security advisories have been resolved in this release:

Refer to the individual advisories for more information about the vulnerabilities that were resolved.

Pull Requests

In addition to the above advisories, the following pull requests were merged to resolve minor security issues:

  • #11580 - reduces user scope of the DataOutput API endpoint
  • #11602 - reduces user scope of the DataImport API endpoint
  • #11579 - improves data security around static and media file access
  • #11659 - adds security banner for superuser accounts

Project Dependencies

We strive to maintain up-to-date dependencies in the InvenTree project, and we have updated a number of dependencies in this release.

New Features

Order Line Numbering

In #11692 we have introduced a “line number” field to external orders, allowing users to specify individual line numbers for each order line. This allows for more flexible ordering and better integration with external systems.

Generic Parameter Filtering

In #11383 we have significantly overhauled the “parameter filtering” system, allowing for more flexible grouping / filtering of parameters.

Import by Natural Keys

#11288 we have added the ability to import data using natural keys, allowing for more intuitive and human-readable data imports. This allows imported data to be mapped to existing database entries using natural keys, rather than relying on internal database IDs. This is particularly useful when migrating data between InvenTree instances, or when importing data from external sources.

Auto-Allocate Tracked Parts

#10887 adds the ability to auto-allocate tracked parts against a build order. This helps to streamline the build allocation process, by providing the auto-allocation feature which has already been available for non-tracked parts.

Copy Data Cells

#11406 introduces the ability to easily copy data directly from table cells. A small but often-requested feature, this allows users to quickly copy data from the InvenTree interface without needing to open individual detail views.

Zero Quantity BOM

In #11437 we have added the ability to create a Bill of Materials (BOM) entry with zero quantity. This allows for more flexible BOM management, particularly in cases where a BOM may be used for reference purposes without needing to specify quantities.

Plugin Cache Busting

#11565 adds a cache-busting mechanism for plugin assets, ensuring that users always receive the latest version of plugin files without needing to manually clear their browser or proxy-server cache. When used in conjunction with the InvenTree plugin creator, this allows plugin developers to easily ensure that users receive the latest version of their plugin assets without needing to worry about caching issues.

Keep Forms Open

#11074 allows certain forms to remain open after submission, allowing users to quickly submit multiple entries without needing to repeatedly open and close the form. This is particularly useful for data entry tasks where multiple similar entries need to be created in quick succession.

Task Monitoring

#11527 introduces the ability to monitor the progress of a single long-running background task via the API. This allows the frontend to provide progress feedback to users when performing long-running operations, and automatically refresh the required data once the task has completed.

Bug Fixes

As always, we have provided a number of bug fixes with this release. Thanks to the many community members who have contributed to identifying and resolving these issues!

Contributing

New Contributors

As always we would like to thank all of our contributors for their hard work and dedication to the InvenTree project. In particular, we would like to welcome the following new contributors who have made their first contributions in this release:

  • @tinpham5614 made their first contribution in https://github.com/inventree/InvenTree/pull/11406
  • @JustusRijke made their first contribution in https://github.com/inventree/InvenTree/pull/11411
  • @jmerro-c3d made their first contribution in https://github.com/inventree/InvenTree/pull/11374
  • @tigger2000ttfn made their first contribution in https://github.com/inventree/InvenTree/pull/11484
  • @justynbell made their first contribution in https://github.com/inventree/InvenTree/pull/11508
  • @Knirps1 made their first contribution in https://github.com/inventree/InvenTree/pull/11512
  • @nino-tan-smartee made their first contribution in https://github.com/inventree/InvenTree/pull/11536
  • @bbzylstra made their first contribution in https://github.com/inventree/InvenTree/pull/10862
  • @amm10090 made their first contribution in https://github.com/inventree/InvenTree/pull/11612
  • @spamik made their first contribution in https://github.com/inventree/InvenTree/pull/11074

Code Contributions

Check out our GitHub page for a list of outstanding issues and feature requests. If you are a developer or want to become one, you can help to contribute to the project by submitting a pull request.

Translation

Our translation efforts continue to grow, with coverage increasing across a wide range of languages. We are grateful to all of our translators who have contributed to making InvenTree accessible to users around the world.

If you are interested in contributing to the translation efforts, please visit our Crowdin project and join the community of translators.

Report Bugs

If you encounter a bug in InvenTree, please report it on our GitHub issues page. Please ensure that you provide as much information as possible to help us diagnose and fix the issue.

Documentation / Technical Writing

If you have experience with technical writing, you can help to improve the InvenTree documentation. We are always looking for help to improve the documentation and make it more accessible to new users.

Financial Support

Sponsorships help to keep this project sustainable, and buys time for the core developers to commit to the project. A recurring or one off sponsorship is a great way to help InvenTree development to continue at full steam!

The work undertaken to keep InvenTree running is done by a very small group of core developers, who do so in their spare time (and are not sponsored by their employers to work on InvenTree). If you benefit from the InvenTree project, please consider contributing to maintain vibrant development of this software!

If you are using InvenTree in a commercial setting, please consider sponsoring the project to help support ongoing development and maintenance. Your support is greatly appreciated and helps to ensure that InvenTree remains a viable and sustainable project for years to come.

If your company benefits from InvenTree, please consider a one time sponsorship or a recurring sponsorship to help support the project.

]]>
SchrodingersGat
1.2.7 Release2026-04-07T00:00:00+00:002026-04-07T00:00:00+00:00/blog/2026/04/07/1.2.7The InvenTree team has now released version 1.2.7, which includes a number of bug fixes related to security issues which have been identified by the community. We recommend all users to update to this version as soon as possible.

Changelog

For a full list of changes made in this release, please refer to the release notes.

Security Advisories

The InvenTree development team has been working closely with the community to identify and resolve security issues in the InvenTree codebase. We have published the following security advisories related to this release:

For specific information regarding the vulnerabilities that have been fixed in this release, please refer to the individual advisories linked above.

Update Procedure

To update to the latest version of InvenTree, please follow the updating instructions provided in the InvenTree documentation. Note that the particular update procedure may vary depending on your installation method.

Acknowledgements

We would like to express our thanks to the community members who have contributed to identifying and resolving security issues in the InvenTree codebase. Your contributions are greatly appreciated and help to make InvenTree a more secure and reliable tool for everyone.

]]>
SchrodingersGat
Action required - Upcoming Security Release2026-03-25T00:00:00+00:002026-03-25T00:00:00+00:00/blog/2026/03/25/security-releaseThe InvenTree core development team has received a report of a critical security vulnerability affecting a large range of releases since 2024. We will release a disclosure and a fixed release for the 1.2.x release series on 2026-04-08 21:00 UTC.
The vulnerability allows for lateral movement and privilege escalation within an InvenTree instance. It has a low attack complexity.

Steps to take now

We are not aware of active exploitation of this vulnerability, but we recommend that users take the following steps to mitigate risks:

  • Do not expose your InvenTree instance to the public internet without hardening steps as laid out in the threat model
  • Ensure registration is disabled till the release
  • Ensure you trust all users registered on your instance, especially those with staff or higher permissions

The vulnerability has a low complexity and can be expected to be exploited once released. It is important to prepare to update or take your system off the public internet.

Security Policy

As always with security related themes we remind all users, security researchers, and intrested parties of our security policy.

If you have discovered a security vulnerability, please report it to us via the channels described in the policy. We take all reports seriously and will work to address any vulnerabilities in a timely manner.

We would like to thank the security researcher who reported this and several other vulnerabilities in a responsible manner, and we encourage others to do the same in the future. The reporter will be credited in the disclosure and CVE entry.

]]>
matmair