EUVD-2026-336429

fkie_cve-2026-55516

Snipe-IT is an IT asset/license management system. Prior to 8.6.2, PATCH or PUT /api/v1/maintenances/{maintenance_id} checks access to the current maintenance record and asset but then fills attacker-controlled fields including asset_id without re-authorizing the newly supplied asset, allowing an authorized user to move a maintenance record onto an asset outside their company scope. This issue is fixed in version 8.6.2.

GHSA-575r-357h-fhch — Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update

Affected: Packagist: snipe/snipe-it

### 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: ```php $maintenance->fill($request->all()); $main…

WID-SEC-W-2026-2073 — Snipe-IT: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Snipe-IT ausnutzen, um Dateien zu manipulieren, um Sicherheitsvorkehrungen zu umgehen, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.

Most recent entries from all

EUVD-2026-336429

fkie_cve-2026-55516

GHSA-575r-357h-fhch — Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update

WID-SEC-W-2026-2073 — Snipe-IT: Mehrere Schwachstellen