CVE-2026-86744: snipe-it before 8.7.0 Race Condition in Asset Checkout
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 checkoutcounter, and two CheckoutableCheckedOut events for a single-assignment asset, corrupting the audit trail and utilization/reconciliation reporting; the asset's final assignedto 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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Snipe-ITto a version that resolves this vulnerability.Fixed in 8.7.0
Event History
Frequently Asked Questions
Who can exploit this issue?
An attacker needs an authenticated Snipe-IT session with the assets.checkout permission or superuser access. They must also send precisely timed concurrent checkout requests for the same available asset.
Are ordinary users or unauthenticated attackers affected?
No. Exploitation requires authenticated, privileged access to perform asset checkouts; the provided information does not indicate an unauthenticated attack path.
What is the practical impact if exploitation succeeds?
The same asset can receive duplicate checkout-history entries, an incremented checkout counter twice, and two checkout events. The final assigned_to value remains singular, but audit-trail and utilization or reconciliation reporting can be corrupted.
What should teams do if they cannot immediately upgrade?
Restrict the assets.checkout permission to only necessary users and monitor checkout history for duplicate near-simultaneous entries involving the same asset. The issue is fixed in version 8.7.0.