Authorization Flaw in Snipe-IT (CVE-2026-86760)
Summary
Vulnerability in Snipe-IT (CVE-2026-86760). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.7.0 or later.
Original description
The description as published by the source.
Snipe-IT versions 8.2.0 through 8.6.x (fixed in 8.7.0) contain an incorrect authorization flaw in app/Http/Controllers/Users/UsersController::update(). The single-user edit route assigned the activated field from the request payload before evaluating the canEditAuthFields authorization gate, so an authenticated non-admin user holding the users.edit permission in the target's company scope can submit a full valid PUT request to /users/{id} and toggle the activated flag on any user, including admin and superuser accounts. Deactivating an admin locks that account out of the application until another admin or superuser re-enables it. Only the activated field is affected; username, email, password and permissions remain protected by the gate, no data is disclosed, and the API (Api\UsersController::update) and bulk-edit paths are not affected.
Source: NIST National Vulnerability Database 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-86760 has been found in Snipe-IT.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade Snipe-IT to 8.7.0 or later.
If unsure, ask your IT team or search "Snipe-IT CVE-2026-86760" on the vendor's site.
CVE-2026-86760 (Snipe-IT) — CWE-863 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 8.7.0 — 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.
Incorrect authorization (CWE-863) exists in Snipe-IT.
Check the vendor advisory for the affected versions of Snipe-IT.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 8.7.0.
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-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-IT' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Snipe-ITを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Snipe-IT to 8.7.0ステージング環境で 8.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com