mirror of
https://github.com/inventree/inventree-website.git
synced 2026-11-20 05:17:45 +00:00
add securoty news
This commit is contained in:
2 files changed
+32
No files matched your search
@@ -0,0 +1,8 @@
|
||||
---
|
||||
author: matmair
|
||||
title: Action required - Upcoming Security Release
|
||||
---
|
||||
|
||||
### Action required - Upcoming Security Release
|
||||
|
||||
There will be a security release for InvenTree on 2026-11-03 21:00 UTC. Please read the [blog post](/blog/2026/11/03/security-release) and prepare to update or take your system off the public internet.
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
author: matmair
|
||||
title: Action required - Upcoming Security Release
|
||||
---
|
||||
|
||||
The 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 21: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](https://docs.inventree.org/en/stable/concepts/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](https://inventree.readthedocs.io/en/stable/security/).
|
||||
|
||||
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.
|
||||
Reference in new issue
Block a user