# CVE-2026-86773

## Summary

- **CVE ID:** CVE-2026-86773
- **Severity:** MEDIUM
- **CVSS Score:** 5.4 (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N)
- **CWE:** CWE-863
- **Published:** Sep 9, 2026
- **Last Modified:** Sep 9, 2026

## Description

Snipe-IT through version 8.6.3 fails to perform object-level authorization in the updateLicense, updateConsumable, updateAccessory, and updateModel endpoints and in the storeModel endpoint for Predefined Kits. The existing check authorizes only the parent Predefined Kit (update on PredefinedKit) and not the child object being attached. As a result, an authenticated user holding only the kits.edit permission can attach a License, Consumable, Accessory, or Asset Model that they are otherwise denied (HTTP 403) from reading directly to a Predefined Kit, and the kit relation index then discloses the attached object's name back to that low-privilege user. This is the update-path and storeModel counterpart to CVE-2026-55478, which fixed only the storeLicense, storeConsumable, and storeAccessory methods in 8.6.2. Note that updateModel was code-vulnerable in 8.6.3 but not reachable in practice because a route-name typo bound the route to a nonexistent controller method, causing HTTP 500 responses. The issue is fixed in Snipe-IT 8.7.0.

## Affected Products

- grokability — snipe-it (8.6.3)
- grokability — snipe-it (8.7.0)

## References

- [CNA](https://github.com/grokability/snipe-it/security/advisories/GHSA-4j5f-mm59-hf9w)
- [CNA](https://www.vulncheck.com/advisories/snipe-it-8.6.3-broken-access-control-via-kit-update-endpoints)

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-09._