Snipe-IT before 8.7.0 Authentication Bypass via API Middleware (CVE-2026-86762) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-86762

Snipe-IT before 8.7.0 Authentication Bypass via API Middleware

Answer in brief

CVE-2026-86762 records a Unknown severity vulnerability in Snipe-IT before 8.7.0 Authentication Bypass via API Middleware. The current sources do not mark it as known exploited. The current feed maps grokability/snipe-it (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 9, 2026Updated Sep 9, 2026Source checked Sep 9, 2026First seen by HOL Sep 9, 2026Material review Sep 9, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps grokability/snipe-it (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
grokability/snipe-itgeneric	>=8.6.3 <8.7.0	8.7.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for grokability/snipe-it.
Review the reported fix. Update grokability/snipe-it to 8.7.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 9, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 9, 2026

Sources and claim methodology

Upstream source description

Snipe-IT before 8.7.0 does not apply the CheckUserIsActivated middleware to the `api` middleware group in app/Http/Kernel.php, and deactivating a user does not revoke that user's Passport personal access tokens. As a result, although a deactivated account is correctly refused at web login, its existing API token continues to authenticate and to grant read and write access to the REST API (assets, users, licenses, etc.) at the account's prior permission level until the token expires. A deactivated account that retains user-management permissions can re-activate itself through the API, permanently defeating the deactivation control.

Quoted source text, attributed separately from HOL analysis.