Skip to main content
CVE-2026-86755VulnerabilityPublished 09/09/2026Updated 09/14/2026

CVE-2026-86755: Incorrect Authorization in grokability snipe-it

Affects grokability snipe-itSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium · fixed in 8.7.0 : update grokability snipe-it when convenient.

Data as of 10/25/2026, 04:40:14 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Exploitation

Not in CISA KEV, no exploitation reported

EPSS
0.2% chance of exploitation in 30 days – higher than 18% 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:L/VI:L/VA:N/SC:N/SI:N/SA:N

What to do

Affected software

ProductAffectedFixed in
grokabilitysnipe-itAffected
  • >=4.2.0 <=8.7.2
Fixed in–
GitHubgrokability/snipe-itpkg:github/grokability/snipe-itOther threatsAffected
  • =4.2.0
  • >=4.2.0 <=8.6.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Snipe-IT to version 8.7.0 or later, where the issue is fixed by adding the can:self.api middleware to the affected routes. Until then, administrative controls on API access may be bypassed by users with valid web sessions and CSRF tokens. Patch status is confirmed fixed in 8.7.0.

Description

Snipe-IT versions 4.2.0 through 8.6.3 expose Laravel Passport's auto-registered personal-access-token routes (GET, POST, DELETE /oauth/personal-access-tokens*) with only 'web' and 'auth:web' middleware, without the self.api permission gate that Snipe-IT enforces on its own token endpoints (/account/api and /api/v1/account/personal-access-tokens). Any user with a valid web session and the corresponding CSRF token can POST to /oauth/personal-access-tokens and mint a long-lived bearer token for their own account, even when an administrator has denied the self.api permission. The issued token is still subject to existing per-endpoint authorization policies, so this is not a privilege escalation; it defeats the administrative control intended to block API/scripted access at the user's own permission level. Fixed in 8.7.0 (commit 3f74b8c), which registers overriding routes wrapped in the can:self.api middleware.

Impact

Users can bypass administrative restrictions that deny API access at their own permission level by minting long-lived bearer tokens via exposed personal-access-token routes. This does not allow privilege escalation beyond the user's own account but defeats intended administrative controls on API access.

References

Community reviews

Loading reviews…