Quick answers
- Is CVE-2026-88894 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88894 being exploited in the wild.
- How severe is CVE-2026-88894?
- Medium severity, with a CVSS score of 5.4, published 10 September 2026.
- Which products and versions are affected?
- Snipe-IT Snipe-IT before 8.7.2.
- Is there a fix for CVE-2026-88894?
- A patch was published on 2026: Fixed in version 8.7.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88894 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-88894?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass (CWE-863) in the PredefinedKitCheckoutService component. The service processes kit checkouts but fails to call the canCheckoutTo() method on items before persisting them to the database, unlike all other checkout paths (single, bulk, API, accessory, license, consumable). With Full Multiple Company Support (FMCS) enabled, an authenticated non-superuser with assets.checkout permission who belongs to at least two companies can POST to /kits/{kit}/checkout with a target user belonging only to company B, and have a company-A asset assigned to that user, violating tenant isolation. The vulnerability requires FMCS to be enabled, the actor to be a multi-company member, and an available asset model in the kit. The issue was introduced when the service was created in 2019 and was fixed in version 8.7.2 by adding company isolation checks before checkout.
Affected products
- Snipe-IT Snipe-IT before 8.7.2
Timeline
- 2026-09-10: disclosed: CVE-2026-88894 published
- 2026: patched: Fixed in version 8.7.2