Authorization Flaw in snipe/snipe-it (CVE-2026-55462)
Summary
Vulnerability in snipe/snipe-it (CVE-2026-55462). Risk of unauthorized operations or information disclosure. Exploitable via GET /users/{user}. Mitigation: upgrade to 374f426f0c or later.
Original description
The description as published by the source.
Snipe-IT is an IT asset/license management system. Prior to 8.6.2, UsersController::show() and printInventory() authorize only user viewing before loading and rendering assigned license, accessory, and consumable relationships, allowing an authenticated user with only users.view to see inventory and cost/order metadata from modules that direct permissions would otherwise deny. This issue is fixed in version 8.6.2.
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-55462 has been found in snipe/snipe-it.
Attackers can target a specific entry point like GET /users/{user} over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade snipe/snipe-it to 374f426f0c or later.
If unsure, ask your IT team or search "snipe/snipe-it CVE-2026-55462" on the vendor's site.
CVE-2026-55462 (snipe/snipe-it) — CWE-863 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /users/{user} / GET /users/{user}/print / GET /licenses / GET /accessories
Patched: 374f426f0c — 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/snipe-it. Attackers reach the vulnerable code path via GET /users/{user}.
Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: GET /users/{user} / GET /users/{user}/print / GET /licenses / GET /accessories.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 374f426f0c.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /users/{user} requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /users/{user}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /users/{user}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade snipe/snipe-it to 374f426f0cステージング環境で 374f426f0c に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /users/{user} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com