Vulnerability in snipe/snipe-it (CVE-2026-55482)
Summary
Vulnerability in snipe/snipe-it (CVE-2026-55482). Risk of unauthorized operations or information disclosure. Exploitable via company_id. Mitigation: upgrade to 8.4.2 or later.
Original description
The description as published by the source.
Impact
The BulkAssetsController::update() method accepts company_id directly from user input without calling Company::getIdForCurrentUser(), the standard company-scoping function used by every other controller in the codebase. A non-superadmin user can move assets across company boundaries, breaking multi-tenancy isolation.
Patches
Patched in https://github.com/grokability/snipe-it/commit/d58fda626e8febfeff4cabbc20ba03edfc411e18
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55482 has been found in snipe/snipe-it.
Attackers can target a specific entry point like company_id over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade snipe/snipe-it to 8.4.2 or later.
If unsure, ask your IT team or search "snipe/snipe-it CVE-2026-55482" on the vendor's site.
CVE-2026-55482 (snipe/snipe-it) — CWE-639 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: company_id
Patched: 8.4.2 — 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.
A vulnerability (CWE-639) exists in snipe/snipe-it. Attackers reach the vulnerable code path via company_id.
Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: company_id.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to 8.4.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'snipe/snipe-it' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'snipe/snipe-it' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
snipe/snipe-itを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade snipe/snipe-it to 8.4.2ステージング環境で 8.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web github.com