CVE-2026-39362
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInvenTree is an Open Source Inventory Management System. Prior to 1.2.7 and 1.3.0, when INVENTREE_DOWNLOAD_FROM_URL is enabled (opt-in), authenticated users can supply remote_image URLs that are fetched server-side via requests.get() with only Django's URLValidator check. There is no validation against private IP ranges or internal hostnames. Redirects are followed (allow_redirects=True), enabling bypass of any URL-format checks. This vulnerability is fixed in 1.2.7 and 1.3.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInvenTree versions prior to 1.2.7 and 1.3.0 contain a Server-Side Request Forgery (SSRF) vulnerability in the remote_image URL download feature. When INVENTREE_DOWNLOAD_FROM_URL is enabled, authenticated users can supply arbitrary URLs that the server fetches via requests.get() with only basic URLValidator checks, without validating against private IP ranges or internal hostnames, and with allow_redirects=True enabling bypass.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.2.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if INVENTREE_DOWNLOAD_FROM_URL is enabledInspect your InvenTree configuration file (typically settings.py or environment variables) or run: grep -r 'INVENTREE_DOWNLOAD_FROM_URL' /path/to/inventree/config/ or check the Django admin interface under InvenTree settings.Affected if The setting is set to True or enabled - this is the primary condition required for the vulnerability to be exploitable
-
Verify the installed InvenTree versionCheck your installed version by running: inventree -V or checking the version file in your installation directory, or looking at the package metadata: pip show inventreeAffected if The installed version is less than 1.2.7 (or 1.3.0) - versions prior to these lack the SSRF protection fix
-
Confirm authenticated user access to image download featureVerify that authenticated users (non-admin) have access to the image upload/download functionality in InvenTree, typically found in the Part or Stock image upload endpoints.Affected if Non-admin authenticated users can access the image download functionality - these are the users who can trigger the SSRF by supplying malicious URLs
You are affected if INVENTREE_DOWNLOAD_FROM_URL is enabled AND your InvenTree version is below 1.2.7 AND authenticated users can access the image download feature, allowing them to supply arbitrary URLs that the server will fetch without private IP/internal hostname validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.2.7
Upgrade to InvenTree 1.2.7 or 1.3.0 to receive the fix, or disable the INVENTREE_DOWNLOAD_FROM_URL setting if immediate upgrading is not feasible.
Upgrade to InvenTree 1.2.7 or 1.3.0 (whichever matches your branch)
- 1. Check current InvenTree version by reviewing your deployed installation or checking the version file (typically in 'src/inventree/version.py' or via the admin interface)
- 2. If running a version before 1.2.7 or 1.3.0, plan for upgrade to version 1.2.7 (for the 1.x stable branch) or 1.3.0 (for the 1.3 branch)
- 3. Backup your database and any custom configurations before upgrading
- 4. For docker deployments: update your image tag to 'inventree/inventree:1.2.7' or 'inventree/inventree:1.3.0' and recreate containers
- 5. For pip installations: run 'pip install inventree==1.2.7' or 'pip install inventree==1.3.0'
- 6. Run database migrations after upgrade ('inv migrate' or per your deployment method)
- 7. Verify the upgrade was successful and the INVENTREE_DOWNLOAD_FROM_URL feature now properly validates against SSRF
- 8. As a temporary mitigation before upgrading, set INVENTREE_DOWNLOAD_FROM_URL=False in your configuration settings to disable the vulnerable feature
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39362 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data