Quick answers
- Is CVE-2026-86773 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86773 being exploited in the wild.
- How severe is CVE-2026-86773?
- Medium severity, with a CVSS score of 5.4, published 9 September 2026.
- Which products and versions are affected?
- Snipe-IT Snipe-IT through 8.6.3.
- Is there a fix for CVE-2026-86773?
- A patch was published on 2026-09-09: Fixed in version 8.7.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86773 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86773?
- Check whether you run Snipeitapp Snipe-It. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
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