# CVE-2026-88894: Snipe-IT before 8.7.2 Authorization Bypass via Predefined Kit Checkout

> Attackers with checkout permissions can bypass company isolation in Snipe-IT to assign assets to users in other companies when Full Multiple Company Support is enabled.

- **Severity:** Medium 5.3 (`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`)
- **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:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-3494-v6qm-q294, GHSA-g7jx-p4xf-m777

## What is CVE-2026-88894?

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

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

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Snipeitapp Snipe-It.

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

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

## Is CVE-2026-88894 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88894 exists.

## 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-88894 and fix it if it is affected.

What it is: CVE-2026-88894 is a medium-severity missing authorization vulnerability in Snipeitapp Snipe-It, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88894 exists.

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-88894/ (Markdown: https://insights.sbomify.com/CVE-2026-88894/index.md)
```

## Sources

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

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