Executive brief
Snipe-IT is an open-source asset and IT management system that administrators can configure to block users from programmatically accessing the API. A flaw in versions 4.2.0 through 8.6.3 allows any authenticated user to bypass this restriction by creating long-lived API tokens through Laravel Passport's default routes, even when their account has been explicitly denied API access. While the issued token is still subject to per-endpoint permission checks, this defeats the administrative control that prevents scripted or automated API access.
Technical details
Snipe-IT exposes Laravel Passport's auto-registered personal-access-token routes (GET, POST, DELETE /oauth/personal-access-tokens*) with only 'web' and 'auth:web' middleware, missing the 'can:self.api' permission gate that Snipe-IT enforces on its own API token endpoints (/account/api and /api/v1/account/personal-access-tokens). An authenticated user with a valid web session and CSRF token can send a POST request to /oauth/personal-access-tokens to generate a bearer token, bypassing the self.api permission check. Attack requires network access, a valid authenticated session, and a CSRF token; no privilege escalation occurs since the issued token is bound by existing per-endpoint authorization policies. The vulnerability was fixed in version 8.7.0 (commit 3f74b8c) by registering overriding routes wrapped in the can:self.api middleware, which takes precedence during route resolution before the Passport service provider routes are loaded.
Affected products
- Snipe-IT Snipe-IT 4.2.0 through 8.6.3
Timeline
- 2026-08-24: disclosed: GitHub Security Advisory GHSA-76pf-qf59-ff3q published
- 2026-09-09: advisory: CVE-2026-86755 published
- 2026-08-24: patched: Fixed in version 8.7.0 with commit 3f74b8c