snipe-it before 8.7.0 Authorization Bypass via API User Create/Update (CVE-2026-86750) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-86750

snipe-it before 8.7.0 Authorization Bypass via API User Create/Update

Answer in brief

CVE-2026-86750 records a Unknown severity vulnerability in snipe-it before 8.7.0 Authorization Bypass via API User Create/Update. 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	>=0 <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 versions <= 8.6.3 (fixed in 8.7.0) do not validate company assignment authorization before persisting user records via the REST API. In Api\UsersController::store() and ::update(), the user record is filled from the request and saved before the requested company_id / company_ids[] values are filtered against the actor's permitted companies (Company::getIdsForCurrentUser()). On installs using Full Multiple Companies Support (FMCS), a non-superuser holding users.create (or users.edit on a target user) can submit company identifiers for companies outside their scope — including a mix of permitted and foreign ids — causing the account row to be committed to the database before authorization is checked. Where null_company_is_floater=1 is set, the post-hoc filter leaves an empty company pivot and the account is persisted as a "floater" with cross-company visibility, allowing creation or relocation of user accounts across tenant boundaries.

Quoted source text, attributed separately from HOL analysis.