Snipe-IT has missing object-level authorization in Kits API
### Impact The API endpoint for adding a license to a predefined kit (`POST /api/v1/kits/{kit_id}/licenses`) only checks whether the caller can edit kits, but does not perform object-level authorization on the referenced license itself. Because of this, a low-privilege user with only predefined-kit permissions can still bind a license that they should not be allowed to access or manage into a kit.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-55478US | medium5.4 | — | ||
Snipe-IT is an IT asset/license management system. Prior to 8.6.2, POST /api/v1/kits/{kit_id}/licenses checks whether the caller can edit kits but does not authorize access to the… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/grokability/snipe-itPACKAGE
- https://github.com/grokability/snipe-it/commit/0d870d540d27107634f3134e0e7f106b3faa6992WEB
- https://github.com/grokability/snipe-it/releases/tag/v8.6.2WEB
- https://github.com/grokability/snipe-it/security/advisories/GHSA-crv3-j83j-f3r6WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-55478ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan