Quick answers
- Is CVE-2026-86754 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86754 being exploited in the wild.
- How severe is CVE-2026-86754?
- High severity, with a CVSS score of 7.3, 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-86754?
- A patch was published on 2026-09-09: Version 8.7.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86754 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86754?
- 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 before version 8.7.0 fails to properly restrict access to Laravel Passport's OAuth client management routes (/oauth/clients endpoints for GET, POST, PUT, DELETE operations). While Snipe-IT's own admin OAuth panel is gated to superusers, the underlying Passport routes are accessible to any authenticated user. An attacker with a valid session can POST to /oauth/clients to register a malicious OAuth client pointing to an attacker-controlled redirect URI. If the attacker then convinces an administrator to click a consent link and approve the client, the resulting authorization code is redirected to the attacker's server. The attacker can exchange this code for a bearer token inheriting the admin's full API permissions and valid for up to 40 years by default. The fix involves overriding the Passport routes in Snipe-IT's route configuration with superuser authorization checks, applied before Passport's service provider loads its own routes.
Affected products
- Snipe-IT Snipe-IT before 8.7.0
Timeline
- 2026-08-24: disclosed
- 2026-09-09: patched: Version 8.7.0 released