# CVE-2026-86750: snipe-it before 8.7.0 Authorization Bypass via API User Create/Update

> Attackers with user creation/edit permissions can bypass company restrictions to create or move users across tenant boundaries in Snipe-IT.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-c929-qxg6-r3mc, GHSA-v9j9-5xx8-fcxj

## What is CVE-2026-86750?

CVE-2026-86750 is a high-severity missing authorization vulnerability in Snipeitapp Snipe-It, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-86750?

It affects 1 product.


Products: Snipeitapp Snipe-It.

## How do I fix CVE-2026-86750?

No fix has been published for CVE-2026-86750 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86750 being exploited?

There is no known exploitation of CVE-2026-86750 in the wild and no public exploit code.

## Other vulnerabilities in Snipeitapp Snipe-It

- [CVE-2025-63601](https://insights.sbomify.com/CVE-2025-63601/): File upload in n/a (critical 9.9)
- [CVE-2026-37709](https://insights.sbomify.com/CVE-2026-37709/): Snipe-IT has insecure permissions in file uploads (critical 9.8)
- [CVE-2026-86738](https://insights.sbomify.com/CVE-2026-86738/): Snipe-IT before 8.7.0 CSS Injection via Custom CSS (critical 9.3)
- [CVE-2026-116199](https://insights.sbomify.com/CVE-2026-116199/): Snipe-IT before 8.6.3 Authentication Bypass via Google SSO Callback (critical 9.2)
- [CVE-2022-1380](https://insights.sbomify.com/CVE-2022-1380/): Stored Cross Site Scripting vulnerability in Item name parameter in snipe/snipe-it (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86750 and fix it if it is affected.

What it is: CVE-2026-86750 is a high-severity missing authorization vulnerability in Snipeitapp Snipe-It, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86750 in the wild and no public exploit code.

Affected product: Snipeitapp Snipe-It. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86750/ (Markdown: https://insights.sbomify.com/CVE-2026-86750/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86750
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86750
- OSV: https://osv.dev/vulnerability/CVE-2026-86750

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86750/
Summaries are generated and may contain mistakes; the official description above is the record.