CVE-2026-86750

published 9 Sep 2026 · updated 14 Sep 2026

snipe-it before 8.7.0 Authorization Bypass via API User Create/Update

7.7HighCVSS 7.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 8.7.0.

Snipe-IT versions <= 8.6.3 (fixed in 8.7.0) do not validate company assignment authorization before persisting user records via the REST API. In Api\UsersController::store() and ::update(), the user record is filled from the request and saved before the requested company_id / company_ids[] values are filtered against the actor's permitted companies (Company::getIdsForCurrentUser()). On installs using Full Multiple Companies Support (FMCS), a non-superuser holding users.create (or users.edit on a target user) can submit company identifiers for companies outside their scope — including a mix of permitted and foreign ids — causing the account row to be committed to the database before authorization is checked. Where null_company_is_floater=1 is set, the post-hoc filter leaves an empty company pivot and the account is persisted as a "floater" with cross-company visibility, allowing creation or relocation of user accounts across tenant boundaries.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
grokability<8.7.08.7.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-86750 severity on Zeptric[![CVE-2026-86750](https://zeptric.io/badge/cve/CVE-2026-86750.svg)](https://zeptric.io/cve/CVE-2026-86750)