Quick answers
- Is CVE-2026-86750 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86750 being exploited in the wild.
- How severe is CVE-2026-86750?
- High severity, with a CVSS score of 7.7, published 9 September 2026.
- Which products and versions are affected?
- Snipe-IT Snipe-IT <= 8.6.3.
- Is there a fix for CVE-2026-86750?
- 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-86750 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86750?
- 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 authorization bypass (CWE-863) in the UsersController::store() and ::update() methods of Snipe-IT's REST API. The root cause is a time-of-check-time-of-use (TOCTOU) flaw: the controller fills and saves the user record from the request body before validating whether the requested company assignments are permitted for the current actor. On systems with Full Multiple Companies Support (FMCS) enabled, a non-superuser holding users.create or users.edit permission can submit company IDs outside their scope—including a mix of permitted and foreign IDs—which get committed to the database before authorization filtering occurs. When null_company_is_floater=1 is configured, the post-hoc filter leaves an empty company pivot, persisting the user as a "floater" with unauthorized cross-company visibility. The attack requires network access and low-privilege credentials (users.create or users.edit role). Patches are available in Snipe-IT 8.7.0 and later, which move authorization filtering before any database writes and add transactional guarantees.
Affected products
- Snipe-IT Snipe-IT <= 8.6.3
Timeline
- 2026-08-24: disclosed
- 2026-09-09: advisory
- 2026-09-09: patched: Fixed in version 8.7.0