Vulnerability in snipe/snipe-it (CVE-2026-55516)
Summary
Vulnerability in snipe/snipe-it (CVE-2026-55516). Data can be tampered with by attackers. Exploitable via PATCH /api/v1/maintenances/{maintenance_id}. Mitigation: upgrade to 8.6.2 or later.
Original description
The description as published by the source.
Impact
The API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.
In a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.
Affected endpoint
PATCH /api/v1/maintenances/{maintenance_id}
Also likely affected:
PUT /api/v1/maintenances/{maintenance_id}
Preconditions
The attacker needs:
- A valid authenticated API token.
- Permission to update asset maintenance records.
- Access to a maintenance record currently attached to an asset in their own company.
The attacker does not need access to the target asset’s company.
Root cause
In the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including asset_id.
The vulnerable behavior is that the new asset_id is not checked against the current user’s company scope before being saved.
Relevant code path:
app/Http/Controllers/Api/MaintenancesController.php
The update method loads the maintenance, checks access to the existing $maintenance->asset, then calls:
$maintenance->fill($request->all());
$maint…
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-55516 has been found in snipe/snipe-it.
Attackers can target a specific entry point like PATCH /api/v1/maintenances/{maintenance_id} over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.7/10.
What to do: upgrade snipe/snipe-it to 8.6.2 or later.
If unsure, ask your IT team or search "snipe/snipe-it CVE-2026-55516" on the vendor's site.
CVE-2026-55516 (snipe/snipe-it) — CWE-639 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PATCH /api/v1/maintenances/{maintenance_id} / PUT /api/v1/maintenances/{maintenance_id} / asset_id
Patched: 8.6.2 — apply immediately
Workaround: Is there a way for users to fix or remediate the vulnerability without upgrading?
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 PATCH /api/v1/maintenances/{maintenance_id}.
Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: PATCH /api/v1/maintenances/{maintenance_id} / PUT /api/v1/maintenances/{maintenance_id} / asset_id.
Severity: High (CVSS 7.7/10). Data can be tampered with by attackers.
Update to 8.6.2.
Workaround: Is there a way for users to fix or remediate the vulnerability without upgrading?
Search webserver/proxy logs for unusual PATCH /api/v1/maintenances/{maintenance_id} 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 'PATCH /api/v1/maintenances/{maintenance_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PATCH /api/v1/maintenances/{maintenance_id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply temporary workaround mitigate
_Is there a way for users to fix or remediate the vulnerability without upgrading?_パッチが適用されるまでの応急処置として、Is there a way for users to fix or remediate the vulnerability without upgrading? を実施。回避策の副作用 (機能低下) を確認した上で。
-
4Apply patch patch
Upgrade snipe/snipe-it to 8.6.2ステージング環境で 8.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
5Post-deployment verification verify
Replay attack against PATCH /api/v1/maintenances/{maintenance_id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com