← Back
CVE-2026-35479
medium
CVSS 6.6
Vulnerability in inventree-project (CVE-2026-35479)
Summary
vulnerability in inventree-project (CVE-2026-35479). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.2.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-35479** has been found in inventree-project.
Risk of unauthorized operations or information disclosure. CVSS score: 6.6/10.
What to do: upgrade inventree-project to **1.2.7** or later.
If unsure, ask your IT team or search "inventree-project CVE-2026-35479" on the vendor's site.
CVE-2026-35479 (inventree-project) — CWE-285 / CVSS v3 6.6
Attack vector: remote (network-reachable) / no user interaction
Patched: `1.2.7` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-285) exists in inventree-project.
📍 Affected scope
inventree-project — .
🔥 Severity
Severity: Medium (CVSS 6.6/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.2.7**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'inventree-project' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'inventree-project' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `inventree-project` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade inventree-project to 1.2.7ステージング環境で 1.2.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。