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.
References
| Link | Resource |
|---|---|
| https://github.com/grokability/snipe-it/commit/f71806b1e0efbd3bc2b6be61994ad2a5d5d6c206 | Patch |
| https://github.com/grokability/snipe-it/security/advisories/GHSA-h992-9438-26v8 | Exploit Vendor Advisory Mitigation Patch |
| https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-race-condition-in-asset-checkout | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-09-09 14:17
Updated : 2026-09-14 20:39
NVD link : CVE-2026-86744
Mitre link : CVE-2026-86744
CVE.ORG link : CVE-2026-86744
JSON object : View
Products Affected
snipeitapp
- snipe-it
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')