CVE-2026-86773: Incorrect Authorization in grokability snipe-it
Affects grokability snipe-itSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 5.3 Medium · fixed in 8.7.0 : update grokability snipe-it when convenient.
Data as of 10/24/2026, 22:16:05 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| grokabilitysnipe-it | Affected
| Fixed in
|
GitHubgrokability/snipe-itpkg:github/grokability/snipe-itOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed in Snipe-IT version 8.7.0. Users should upgrade to version 8.7.0 or later to remediate this issue. Patch status is not explicitly stated beyond this fix version, so verify with the vendor advisory for the latest remediation guidance. No other mitigations are indicated.
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.
Impact
An authenticated user with limited permissions (kits.edit) can attach child objects (License, Consumable, Accessory, Asset Model) to Predefined Kits even if they lack read access to those objects. This leads to unauthorized disclosure of the attached object's name via the kit relation index. There is no indication of privilege escalation beyond this information disclosure or remote code execution. The CVSS 4.0 base score is 5.3 (medium severity), reflecting network attack vector, low complexity, no user interaction, and limited confidentiality and integrity impact.
Summary
CVE-2026-86773 describes an incorrect authorization vulnerability in Snipe-IT through version 8.6.3. The affected endpoints (updateLicense, updateConsumable, updateAccessory, updateModel, and storeModel for Predefined Kits) perform authorization checks only on the parent Predefined Kit, not on the child objects being attached. This allows users with kits.edit permission but without read permission on the child objects to attach those objects to a Predefined Kit and receive the attached object's name in the kit relation index, resulting in unauthorized information disclosure. The updateModel endpoint was vulnerable in code but not exploitable due to a routing error causing HTTP 500 responses. This vulnerability complements CVE-2026-55478, which addressed related methods in version 8.6.2. The vulnerability is resolved in Snipe-IT 8.7.0.