Executive brief
Snipe-IT is an IT asset management platform used by organizations to track hardware, software licenses, and consumables. An authenticated user with limited permissions (kits.edit only) can attach licenses, consumables, or accessories they should not be able to access to a Predefined Kit, and then retrieve the names of those restricted objects. While this does not corrupt the objects themselves, it allows unauthorized information disclosure and unintended data associations.
Technical details
The vulnerability is a broken access control issue (CWE-863) in five API endpoints: updateLicense, updateConsumable, updateAccessory, updateModel, and storeModel in PredefinedKitsController.php. These endpoints perform authorization only on the parent Predefined Kit (via $this->authorize('update', PredefinedKit::class)) but fail to authorize the child object (license, consumable, accessory, or asset model) being attached via syncWithoutDetaching or attach. An authenticated user with kits.edit permission can thus attach restricted objects without ever fetching or authorizing them, and the kit relation index then leaks the attached object's name back to the user. No user interaction is required; exploitation occurs over the network via HTTP PUT/POST requests. The updateModel endpoint was further unreachable due to a route typo but contained the same authorization flaw. The vulnerability is fixed in Snipe-IT 8.7.0.
Affected products
- Snipe-IT Snipe-IT through 8.6.3
Timeline
- 2026-09-09: disclosed
- 2026-09-09: patched: Fixed in version 8.7.0