Quick answers
- Is CVE-2026-86767 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86767 being exploited in the wild.
- How severe is CVE-2026-86767?
- Medium severity, with a CVSS score of 5, published 9 September 2026.
- Which products and versions are affected?
- Snipe-IT Snipe-IT before 8.7.0.
- Is there a fix for CVE-2026-86767?
- A patch was published on 2026-06-22: Fix committed to develop branch (commit fbf441f2a2) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86767 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-86767?
- 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 an incorrect authorization check (CWE-200, CWE-863) in the GET /hardware/requested endpoint. The root cause is twofold: (1) the CheckoutRequest model lacks company scope filtering, and (2) the authorize() call passes Asset::class as a string rather than a model instance, causing the authorization policy to bypass the per-record company scope check and collapse to a simple permission check (assets.view). An authenticated user with the routine assets.view permission can issue a single unmodified GET request to retrieve the entire cross-tenant list of pending asset requests. No parameter manipulation or user interaction is required. The vulnerability affects all FMCS-enabled installations running v8.6.3 or earlier; it was fixed in the develop branch on 2026-06-22 and ships in v8.7.0.
Affected products
- Snipe-IT Snipe-IT before 8.7.0
Timeline
- 2026-08-24: disclosed: GitHub security advisory published
- 2026-06-22: patched: Fix committed to develop branch (commit fbf441f2a2)
- 2026-09-09: advisory: NVD advisory published; CVE-2026-86767 assigned