{"id":"CVE-2026-55516","aliases":["GHSA-575r-357h-fhch"],"title":"Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update","summary":"Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update","severity":"high","cvss":7.7,"cwe":["CWE-639"],"vendor":"snipe","product":"snipe/snipe-it","ecosystem":"composer","affected":["snipe/snipe-it <= 8.6.1"],"patched":["snipe/snipe-it 8.6.2"],"published":"2026-08-28","updated":"2026-08-28","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-575r-357h-fhch","references":[{"url":"https://github.com/grokability/snipe-it/security/advisories/GHSA-575r-357h-fhch"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-55516"},{"url":"https://github.com/grokability/snipe-it/commit/905d498ecdb0ee5591231c97bf48435e92044368"},{"url":"https://github.com/grokability/snipe-it/releases/tag/v8.6.2"},{"url":"https://github.com/advisories/GHSA-575r-357h-fhch"}],"tags":["ghsa","composer"],"epss":0.00376,"epssPercentile":0.31493,"ingestedAt":"2026-08-28T18:23:37.427Z","slug":"CVE-2026-55516","body":"## Overview\n\n### Impact\nThe 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.\n\nIn 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.\n\n###  Affected endpoint\n`PATCH /api/v1/maintenances/{maintenance_id}`\n\nAlso likely affected:\n\n`PUT /api/v1/maintenances/{maintenance_id}`\n\n### Preconditions\nThe attacker needs:\n- A valid authenticated API token.\n- Permission to update asset maintenance records.\n- Access to a maintenance record currently attached to an asset in their own company.\n\nThe attacker does not need access to the target asset’s company.\n\n### Root cause\nIn the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.\n\nThe vulnerable behavior is that the new asset_id is not checked against the current user’s company scope before being saved.\n\n### Relevant code path:\n`app/Http/Controllers/Api/MaintenancesController.php`\n\nThe update method loads the maintenance, checks access to the existing $maintenance->asset, then calls:\n```php\n$maintenance->fill($request->all());\n$maintenance->save();\n```\n\nSince `asset_id` is fillable on the maintenance model, the attacker can re-parent the record to another company’s asset.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n### Security impact\nThis breaks tenant/company isolation in multi-company deployments. A scoped user can write maintenance records against assets outside their authorized company boundary.\n\nPotential impact includes:\n- Cross-company asset history pollution.\n- Unauthorized modification of another company’s asset maintenance timeline.\n- Incorrect maintenance, cost, audit, and warranty records on victim-company assets.\n- Loss of integrity in asset lifecycle records.\n\nThis is not intended functionality because the application’s company-scoping model should prevent users from writing records onto inaccessible assets.\n\n## Affected packages\n\n- `snipe/snipe-it <= 8.6.1`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `snipe/snipe-it 8.6.2`","depth":"twilight","depthScore":42,"depthScoreParts":{"impact":42.4,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}