CVE-2026-86762: Missing Authorization in grokability snipe-it
Affects grokability snipe-itSource CVE Database V5
Not known to be exploited · CVSS 8.6 High · fixed in 8.7.0 : patch grokability snipe-it soon.
Data as of 10/25/2026, 04:40:14 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| grokabilitysnipe-it | Affected
| Fixed in
|
GitHubgrokability/snipe-itpkg:github/grokability/snipe-itOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Snipe-IT version 8.7.0 that applies the CheckUserIsActivated middleware to the API middleware group and revokes personal access tokens upon user deactivation. Users should upgrade to version 8.7.0 or later to remediate this vulnerability. Until upgraded, manual revocation of personal access tokens for deactivated users is recommended to mitigate risk.
Description
Snipe-IT versions before 8.7.0 do not enforce user activation status on API access, allowing deactivated users' existing API tokens to continue granting access. This flaw permits deactivated users with management permissions to reactivate themselves via the API, bypassing deactivation controls.
Impact
Deactivated users retain API access through existing tokens, enabling unauthorized read and write operations on sensitive resources. Users with user-management permissions can reactivate their own accounts via the API, permanently defeating the intended deactivation control. This poses a significant risk of unauthorized data access and privilege escalation within affected Snipe-IT deployments.
Summary
CVE-2026-86762 describes a missing authorization check in Snipe-IT before version 8.7.0. The application fails to apply the CheckUserIsActivated middleware to the API middleware group, and deactivating a user does not revoke their Passport personal access tokens. Consequently, API tokens issued before deactivation remain valid, allowing continued read and write access to the REST API at the user's previous permission level. This includes access to assets, users, licenses, and other resources. A user with management permissions who has been deactivated can use the API to reactivate their account, effectively circumventing the deactivation mechanism.
References
- github.com/grokability/snipe-it/security/advisories/GHSA-cj4w-vx6j-42rf (opens in a new tab)
- github.com/grokability/snipe-it/commit/b3f12f974bb2c0175ea68dad163ed04726db4280 (opens in a new tab)
- vulncheck.com/advisories/snipe-it-before-8.7.0-authentication-bypass-via-api-middleware (opens in a new tab)