Quick answers
- Is CVE-2026-86755 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86755 being exploited in the wild.
- How severe is CVE-2026-86755?
- Medium severity, with a CVSS score of 5.4, published 9 September 2026.
- Which products and versions are affected?
- Snipe-IT Snipe-IT 4.2.0 through 8.6.3.
- Is there a fix for CVE-2026-86755?
- A patch was published on 2026-08-24: Fixed in version 8.7.0 with commit 3f74b8c Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86755 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86755?
- 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
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