Snipe-IT before 8.7.2 Authorization Bypass via Predefined Kit Checkout (CVE-2026-88894) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-88894

Snipe-IT before 8.7.2 Authorization Bypass via Predefined Kit Checkout

Answer in brief

CVE-2026-88894 records a Unknown severity vulnerability in Snipe-IT before 8.7.2 Authorization Bypass via Predefined Kit Checkout. 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 10, 2026Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 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	>=0 <8.7.2	8.7.2

Recommended response

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

Evidence timeline and material changes

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

Sources and claim methodology

Upstream source description

Snipe-IT's predefined kit checkout path does not enforce Full Multiple Company Support (FMCS) tenant isolation on the checkout target. Unlike the single, bulk, API, accessory, license and consumable checkout paths, App\Services\PredefinedKitCheckoutService never calls $item->canCheckoutTo($target); it only performs the actor-vs-item policy check and an availability check before persisting the checkout. With FMCS enabled, a non-superuser who belongs to at least two companies and holds the assets.checkout permission can POST to /kits/{kit}/checkout with a user_id belonging only to company B and have a company-A asset (and likewise kit licenses, consumables and accessories) assigned to that user, bypassing the company-mismatch check that blocks the same operation on every other checkout path. The issue is fixed in Snipe-IT 8.7.2; it was runtime-verified on v8.6.3 and code-inspected on v8.7.1, and the affected service has lacked the check since 2019, so earlier FMCS deployments are likely also affected.

Quoted source text, attributed separately from HOL analysis.