# CVE-2026-86744

## Summary

- **CVE ID:** CVE-2026-86744
- **Severity:** LOW
- **CVSS Score:** 2.2 (CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N)
- **CWE:** CWE-362
- **Published:** Sep 9, 2026
- **Last Modified:** Sep 9, 2026

## Description

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 Products

- grokability — snipe-it (0)
- grokability — snipe-it (8.7.0)

## References

- [CNA](https://github.com/grokability/snipe-it/security/advisories/GHSA-h992-9438-26v8)
- [CNA](https://github.com/grokability/snipe-it/commit/f71806b1e0efbd3bc2b6be61994ad2a5d5d6c206)
- [CNA](https://www.vulncheck.com/advisories/snipe-it-before-8.7.0-race-condition-in-asset-checkout)

## Exploitation Prediction (EPSS)

- **EPSS Score:** 0.21%
- **EPSS Percentile:** 10.6

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-11._