CVE-2026-86744
Snipe-IT 8.6.3 and earlier (and develop pre-release commits prior …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/grokability/snipe-it/commit/f71806b1e0efbd3bc2b6be61994ad2a5d5d6c206
- github.com/grokability/snipe-it/security/advisories/GHSA-h992-9438-26v8
- www.vulncheck.com/advisories/snipe-it-before-8.7.0-race-condition-in-asset-checkout
- nvd.nist.gov/vuln/detail/CVE-2026-86744
- cve.org/CVERecord?id=CVE-2026-86744
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.