CVE-2026-86744

published 9 Sep 2026 · updated 18 Sep 2026

snipe-it before 8.7.0 Race Condition in Asset Checkout

2.2LowCVSS 2.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 8.7.0.

Snipe-IT 8.6.3 and earlier (and develop pre-release commits prior to the fix) contain a race condition in the asset checkout paths. Api\AssetsController::checkout() and Assets\AssetCheckoutController::store() call Asset::availableForCheckout() outside the mutation path and then invoke Asset::checkOut() without taking a row lock or re-checking availability, so two concurrent checkout requests for the same available asset can both observe it as available and both commit. This produces duplicate checkout-history rows, a doubled checkout_counter, and two CheckoutableCheckedOut events for a single-assignment asset, corrupting the audit trail and utilization/reconciliation reporting; the asset's final assigned_to remains singular, so the visible assignment stays intact. Exploitation requires an authenticated session holding the assets.checkout permission (or superuser) and precise concurrent timing. Fixed in 8.7.0.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
grokability<8.7.08.7.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-86744 severity on Zeptric[![CVE-2026-86744](https://zeptric.io/badge/cve/CVE-2026-86744.svg)](https://zeptric.io/cve/CVE-2026-86744)