VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

inventree: vulnerability history, versions and safety

inventree is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 64 releases, from Jun 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded H4 M3 U3
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all inventree vulnerabilities

Vulert verdict on inventree 0.24.1 i

Updated on 23 Oct 2026

Careful: 0.24.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.24.1 — affected i
  • Vulnerabilities on record 10 over 4 years · 3 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Depended on by 6 packages i
  • Stars 50 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for inventree, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.24.1 21 Oct 2026 H1 non-standard No Details →
0.24.0 20 Oct 2026 H1 non-standard No Details →
0.23.2 13 May 2026 H1 non-standard No Details →
0.23.1 02 Mar 2026 H1 non-standard No Details →
0.23.0 15 Feb 2026 H1 non-standard No Details →
0.22.0 11 Feb 2026 H1 non-standard No Details →
0.21.1 06 Jan 2026 H1 non-standard No Details →
0.21.0 06 Jan 2026 H1 non-standard No Details →
0.20.0 02 Dec 2025 H1 non-standard No Details →
0.19.0 03 Sep 2025 H1 non-standard No Details →
0.18.0 16 Aug 2025 H1 non-standard No Details →
0.17.5 27 Mar 2025 H1 MIT No Details →
0.17.4 05 Feb 2025 H1 MIT No Details →
0.17.3 13 Jan 2025 H1 MIT No Details →
0.17.2 16 Dec 2024 H1 MIT No Details →
0.17.1 09 Oct 2024 H1 MIT No Details →
0.17.0 10 Sep 2024 H1 MIT No Details →
0.16.1 07 Aug 2024 H1 M1 MIT No Details →
0.14.0 03 Jun 2024 H1 M1 MIT No Details →
0.13.5 09 May 2024 H1 M1 MIT No Details →
0.13.4 30 Apr 2024 H1 M1 MIT No Details →
0.13.3 30 Jan 2024 H1 M1 MIT No Details →
0.13.2 11 Dec 2023 H1 M1 MIT No Details →
0.13.1 23 Nov 2023 H1 M1 MIT No Details →
0.13.0 21 Nov 2023 H1 M1 MIT No Details →
0.12.2 08 Sep 2023 H1 M1 MIT No Details →
0.12.1 26 Jul 2023 H1 M1 MIT No Details →
0.12.0 17 Jul 2023 H1 M1 MIT No Details →
0.11.2 21 Apr 2023 H1 M1 MIT No Details →
0.11.1 20 Apr 2023 H1 M1 MIT No Details →
0.11.0 17 Apr 2023 H1 M1 MIT No Details →
0.10.1 23 Feb 2023 H1 M1 MIT No Details →
0.10.0 03 Feb 2023 H1 M1 MIT No Details →
0.9.2 12 Dec 2022 H1 M1 MIT No Details →
0.9.1 04 Dec 2022 H1 M1 MIT No Details →
0.9.0 26 Oct 2022 H1 M1 MIT No Details →
0.8.3 05 Sep 2022 H1 M1 MIT No Details →
0.8.2 28 Aug 2022 H1 M2 U1 MIT No Details →
0.8.1 02 Aug 2022 H1 M2 U1 MIT No Details →
0.8.0 29 Jul 2022 H1 M2 U1 MIT No Details →
0.7.3 11 Jul 2022 H1 M2 U1 MIT No Details →
0.7.2 19 Jun 2022 H1 M2 U1 MIT No Details →
0.7.1 03 Jun 2022 H4 M3 U3 MIT No Details →
0.7.0 19 May 2022 H4 M3 U3 MIT No Details →
0.6.1 17 May 2022 H4 M3 U3 MIT No Details →
0.6.0 20 Feb 2022 H4 M3 U3 MIT No Details →
0.4.4 09 Aug 2021 H4 M3 U3 MIT No Details →
0.3.2 26 Jul 2021 H4 M3 U3 MIT No Details →
0.3.1 19 Jul 2021 H4 M3 U3 MIT No Details →
0.2.4 27 Jun 2021 H4 M3 U3 MIT No Details →
0.1.4 16 Apr 2021 H4 M3 U3 MIT No Details →
0.1.3 05 Mar 2021 H4 M3 U3 MIT No Details →
0.1.2 08 Jan 2021 H4 M3 U3 MIT No Details →
0.1.1 05 Dec 2020 H4 M3 U3 MIT No Details →
0.1.0 28 Sep 2020 H4 M3 U3 MIT No Details →
0.0.9 28 May 2020 H4 M3 U3 MIT No Details →
0.0.8 19 May 2020 H4 M3 U3 MIT No Details →
0.0.7 18 May 2020 H4 M3 U3 MIT No Details →
0.0.6 17 May 2020 H4 M3 U3 MIT No Details →
0.0.5 16 May 2020 H4 M3 U3 MIT No Details →
0.0.4 13 May 2020 H4 M3 U3 MIT No Details →
0.0.3 12 May 2020 H4 M3 U3 MIT No Details →
0.0.2 11 May 2020 H4 M3 U3 MIT No Details →
0.0.1 11 May 2020 H4 M3 U3 MIT No Details →

All 64 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 6
  • 2024 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 10 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for inventree

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-2111: Unrestricted Attachment Upload in inventree 8.8 high 0.7.2 17 Jun 2022
CVE-2022-2112: CSV Injection in inventree 8.8 high 0.7.2 18 Jun 2022
CVE-2022-2112: inventree CSV Injection Vulnerability 8.8 high 0.7.2 06 Jul 2026
CVE-2022-2111: InvenTree Unrestricted Attachment Upload Vulnerability 8.8 high 0.7.2 06 Jul 2026
CVE-2022-3355: Inventree Stored Cross-site Scripting Vulnerability 5.4 medium 0.8.3 30 Sep 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About inventree

Is inventree safe to use?

Vulert records 10 vulnerabilities for inventree in PyPI: 0 critical, 4 high, 3 medium and 0 low, plus 3 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is inventree's Vulert package health score?

Vulert scores inventree 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of inventree affected?

Yes. 0.24.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does inventree have?

10 vulnerabilities are recorded for inventree in the PyPI ecosystem: 0 critical, 4 high, 3 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new inventree vulnerabilities disclosed?

3 vulnerabilities were recorded for inventree in the last 12 months, and the oldest entry in this database dates to 17 Jun 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of inventree are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor inventree for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the inventree version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.